| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
code. There are only a handful of MSRs common between the two so there isn't
too much duplicate functionality.
The VT-x code has the following types of MSRs:
- MSRs that are unconditionally saved/restored on every guest/host context
switch (e.g., MSR_GSBASE).
- MSRs that are restored to guest values on entry to vmx_run() and saved
before returning. This is an optimization for MSRs that are not used in
host kernel context (e.g., MSR_KGSBASE).
- MSRs that are emulated and every access by the guest causes a trap into
the hypervisor (e.g., MSR_IA32_MISC_ENABLE).
Reviewed by: grehan
|
|
|
|
|
|
|
|
| |
Fix style issues noticed when I went to MFC r257820
MFC after: 2 days
X-MFC-With: r257820
Sponsored by: Multiplay
|
|
|
|
|
|
|
|
| |
reload also if that size was not specified in the new configuration.
Previously it happened only if size was explicitly changed in config.
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
setpgid(2) is more portable than setpgrp(2).
The BSD variant of setpgrp is a wrapper for
setpgid(2) anyways.
MFC after: 5 weeks
|
|
|
|
|
|
|
|
|
|
|
| |
Makefiles should not assume that source files can be overwritten. This is the
common case for Perforce source trees.
This is a followup commit to r211243 in the same vein.
MFC after: 1 month
Sponsored by: Spectra Logic
MFSpectraBSD: r1036319 on 2014/01/29, r1046711 on 2014/03/06
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the minimum image size specified is always less than the maximum
image size. If makefs(1) is invoked specifying minimum image size,
but not maximum one, the program exits with an error. Example:
# sudo -E makefs -M 538968064 -B be /home/davide/disk.img $DESTDIR
makefs: `/home/davide/tftproot/mips' minsize of 538968064 rounded up
to ffs bsize of 8192 exceeds maxsize 0. Lower bsize, or round the
minimum and maximum sizes to bsize.
Assert then that minsize < maxsize iff maxsize is specified.
This change allows me to build MIPS images using makefs(1) and following
what specified in the wiki again.
Reviewed by: jmallett, ngie
|
|
|
|
|
|
|
|
| |
longer considered 'experimental.'
Reviewed by: grehan
MFC after: 3 days
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
| |
MFC after: 3 days
Sponsored by: The FreeBSD Foundation
|
|
|
|
| |
people.
|
|
|
|
|
|
|
|
|
|
| |
installer via UEFI that we do not support booting ZFS via UEFI yet
PR: 193595
Approved by: nwhitehorn
MFC after: 5 days
Sponsored by: ScaleEngine Inc.
CR: https://reviews.freebsd.org/D782
|
|
|
|
|
|
|
|
|
| |
Resolve a markup mistake
Reviewed by: trasz
Approved by: bcr (mentor), wblock (mentor)
Sponsored by: ScaleEngine Inc.
CR: https://reviews.freebsd.org/D735
|
|
|
|
|
|
|
| |
reality. In particular, draw a connection between the auto ZFS script and
the auto UFS one, since they fulfill similar functions. I'm not sure the
auto ZFS code is actually experimental anymore, so it might be worth
changing that label still.
|
|
|
|
| |
just pressing enter repeatedly to successfully install a reasonable system.
|
|
|
|
|
|
|
|
|
| |
Cross reference it from iscsid(8) and iscsictl(8)
Reviewed by: trasz
Approved by: bcr (mentor), wblock (mentor)
Sponsored by: ScaleEngine Inc.
CR: https://reviews.freebsd.org/D741
|
|
|
|
|
| |
Submitted by: Kurt Lidl (original version)
MFC after: 6 weeks
|
|
|
|
|
|
|
| |
It allows to bypass range checks between UNMAP and READ/WRITE commands,
which may introduce additional delays while waiting for UNMAP parameters.
READ and WRITE commands are always processed in safe order since their
range checks are almost free.
|
|
|
|
|
| |
Default values are "on". Disabling requires backend to support IO_DIRECT
and IO_SYNC flags respectively, or some alternatives.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
many thanks for their continued support of FreeBSD.
While I'm there, also implement a new build knob, WITHOUT_HYPERV to
disable building and installing of the HyperV utilities when necessary.
The HyperV utilities are only built for i386 and amd64 targets.
This is a stable/10 candidate for inclusion with 10.1-RELEASE.
Submitted by: Wei Hu <weh microsoft com>
MFC after: 1 week
|
|
|
|
|
|
| |
Submitted by: bjk
Approved by: bcr (mentor)
Sponsored by: ScaleEngine Inc.
|
|
|
|
|
|
| |
Reviewed by: trasz
Approved by: bcr (mentor)
Sponsored by: ScaleEngine Inc.
|
|
|
|
|
|
|
| |
Note that independent of this change a readonly disk file would still be
opened O_RDONLY and protected from writes by the guest.
Reviewed by: grehan
|
|
|
|
|
|
|
|
|
| |
if we got a Login Response PDU without the "T" bit set, try again with
an empty request. This fixes interoperability with COMSTAR.
Reviewed by: mav@
Tested by: mav@
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
merge(1), which is part of the RCS package, it must not be installed if
WITHOUT_RCS update is set. Otherwise, it will produce confusing errors.
CR: https://reviews.freebsd.org/D691
MFC after: 1 week
Sponsored by: Spectra Logic
|
|
|
|
| |
CID: 1229996
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
NetBSD's virtio-net implementation doesn't negotiate
the merged rx-buffers feature. To support this, check
to see if the feature was negotiated, and then adjust
the operation of the receive path accordingly by using
a larger iovec, and a smaller rx header.
In addition, ignore writes to the (read-only) status byte.
Tested with NetBSD/amd64 5.2.2, 6.1.4 and 7-beta.
Reviewed by: neel, tychon
Phabric: D745
MFC after: 3 days
|
|
|
|
| |
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
|
|
|
|
| |
when the initiator skips security negotiation. This fixes interoperability
with Xtend SAN initiator.
PR: 193021
MFC after: 1 week
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
|
| |
Submitted by: luigi
Obtained from: Vincenzo Maffione, Universita` di Pisa
MFC after: 3 days
|
|
|
|
|
|
| |
PR: 188931
Submitted by: Takefu <takefu@airport.fm>
MFC after: 3 days
|
|
|
|
|
| |
MFC after: 2 weeks
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
| |
MFC after: 2 weeks
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
|
|
|
| |
into assertions.
Discussed with: mav@
MFC after: 2 weeks
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
|
|
|
|
|
| |
Note that this is a workaround, not a proper solution. If you know
lex well, and want to help - please let me know, I'll explain how it
should work.
PR: 192968
MFC after: 1 week
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
| |
MFC after: 2 weeks
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
|
| |
is to set OPTIND to 1, not unset it (which causes an error).
Thanks to: jilles
|
|
|
|
|
|
|
|
| |
used prior to f_dialog_init() -- e.g., in a script that sets
DIALOG_SELF_INITIALIZE to NULL, preventing f_dialog_init() from being run
automaticaly when `dialog.subr' is included. Caused by sub-shell processing
of arguments inheriting prior value of $OPTIND, used by getopts. Solved by
unsetting OPTIND prior to [re-]processing of positional arguments.
|
|
|
|
|
|
|
|
|
|
| |
While there, add a NO_WTHREAD_SAFETY flag that can be used to disable
this specific warning flag. Disable it for auditdistd. We can easily
patch up auditdistd to have the right annotations to build, but as
auditdistd is intended to be portable across other operating systems,
it's not worth the effort.
Approved by: brueffer@
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
packets at all. Swapping byte order on SOCK_RAW was actually a bug, an
artifact from the BSD network stack, that used to convert a packet to
native byte order once it is received by kernel.
Other operating systems didn't follow this, and later other BSD
descendants fixed this, leaving us alone with the bug. Now it is
clear that we should fix the bug.
In collaboration with: Olivier Cochard-Labbé <olivier cochard.me>
See also: https://wiki.freebsd.org/SOCK_RAW
Sponsored by: Nginx, Inc.
|
|
|
|
|
|
| |
in the emulation of the task switch. If any exceptions are triggered then the
guest %rip should point to instruction that caused the task switch as opposed
to the one after it.
|
|
|
|
|
|
|
|
|
| |
env var if set)
Phabric: https://reviews.freebsd.org/D412
Reviewed by: bdrewery
MFC after: 2 weeks
Relnotes: yes
|
|
|
|
| |
MFC after: 3 dayS
|
|
|
|
|
|
| |
for systems with vt(4) consoles.
MFC after: 3 days
|
|
|
|
|
| |
path even under vt, which is no longer useful, since the syscons keymap
files have been converted and committed for use by vt.
|
|
|
|
|
|
|
|
|
|
| |
Also, add a missing LIBPANEL dependency for lldb
Approved by: rpaulo (mentor)
Suggested by: brooks
MFC after: 5 days
Phabric: D675 (as part of a larger diff)
PR: 192762
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
containing whitespace.
PR: 192947
MFC after: 2 weeks
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
|
|
|
| |
it was set, now it's conditional.
PR: 192862
MFC after: 2 weeks
Sponsored by: The FreeBSD Foundation
|