Page MenuHomeFreeBSD

bhyve: provide basic descriptions for VMX exit reason
ClosedPublic

Authored by yuripv on Oct 12 2018, 10:43 AM.
Tags
None
Referenced Files
Unknown Object (File)
Dec 20 2023, 12:57 AM
Unknown Object (File)
Nov 20 2023, 9:32 PM
Unknown Object (File)
Nov 10 2023, 4:38 PM
Unknown Object (File)
Nov 10 2023, 4:09 PM
Unknown Object (File)
Nov 7 2023, 9:29 PM
Unknown Object (File)
Oct 27 2023, 7:31 AM
Unknown Object (File)
Oct 19 2023, 8:21 PM
Unknown Object (File)
Oct 9 2023, 3:36 PM

Details

Summary

Provide basic descriptions for VMX exit reason (from "Intel® 64 and IA-32 Architectures Software Developer’s Manual Volume 3"). Add the document to SEE ALSO in bhyve.8 (and pet manlint here a bit).

It makes it a bit easier to understand the reason of exit, e.g.:

vm exit[0]
        reason          VMX
        rip             0x000000000000fff0
        inst_length     3
        status          0
        exit_reason     48 (EPT violation)
        qualification   0x0000000000000184
        inst_type               0
        inst_error              0
Abort trap

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

0mp added a subscriber: 0mp.

The manual page update seems fine from the mdoc perspective.

This revision is now accepted and ready to land.Oct 12 2018, 10:56 AM
This revision now requires review to proceed.Oct 12 2018, 10:56 AM
usr.sbin/bhyve/bhyverun.c
92 ↗(On Diff #49049)

const char * const ? If it passes over other places.

93 ↗(On Diff #49049)

Use designated initializers, even if the indexes do not have symbolic names. Put each initialization element on its own line.

548 ↗(On Diff #49049)

I would create a static function which does the calculation of the string by number.

yuripv added inline comments.
usr.sbin/bhyve/bhyverun.c
93 ↗(On Diff #49049)

Done, I hope that including <amd64/vmm/intel/vmcs.h> is OK here.

kib added inline comments.
usr.sbin/bhyve/bhyverun.c
587 ↗(On Diff #49052)

Blank line is needed after '{' if no locals are defined.

590 ↗(On Diff #49052)

This blank line is excessive.

93 ↗(On Diff #49049)

This header is not installed, so bhyve(8) definitely requires the build from the full sources. I remember that it was the case already due to vmm_instructions_emul.c.

This revision is now accepted and ready to land.Oct 12 2018, 12:20 PM
This revision now requires review to proceed.Oct 12 2018, 2:44 PM
This revision is now accepted and ready to land.Oct 12 2018, 3:03 PM

Can I proceed with kib being the reviewer for this, or bhyve group will take a look?

The bhyve group hat was requested by Peter Grehan for "Maintainer" approval and awareness of bhyve bits, as far as I can see this review does not touch any bits that need bhyve maintainer approval, so you can commit with out an accept from them.

I am accepting this as me personally, I am not a person who can wear hat bhyve maintainer.

jhb added a subscriber: jhb.
jhb added inline comments.
usr.sbin/bhyve/bhyve.8
503 ↗(On Diff #49057)

I think the doc folks would want all of the formatting changes to this file be done as a separate commit from the actual content change. I think adding the reference to the Intel SDM manual is the only content change to this file?

yuripv added inline comments.
usr.sbin/bhyve/bhyve.8
503 ↗(On Diff #49057)

Yes, the only content change is added reference. Formatting changes are mostly pointed out by mandoc lint, and seem to be formally accepted by manpages (@0mp).

Hi @yuripv , is there anything pending for this patch to be committed?

Hi @yuripv , is there anything pending for this patch to be committed?

Sorry for the delay, submitted to mentor for approval.

This revision was automatically updated to reflect the committed changes.