From: Andre Przywara <andre.przywara@amd.com>
To: "Cui, Dexuan" <dexuan.cui@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH] x86/hvm: accelerate I/O intercept handling
Date: Wed, 31 Mar 2010 12:08:08 +0200 [thread overview]
Message-ID: <4BB31F08.20403@amd.com> (raw)
In-Reply-To: <ED3036A092A28F4C91B0B4360DD128EABE0C080F@shzsmsx502.ccr.corp.intel.com>
Cui, Dexuan wrote:
> Actually in 15425:6e934c799051, VMX once enabled the feature, but IIRC,
> later Keir removed that in some cleanup patches and let the
> EXIT_REASON_IO_INSTRUCTION handler invoke handle_mmio() also -- I don't
> remember how people commented the slowness of IN/OUT emulation caused
> the change...
If I got this correctly, 15425 introduces only the OUTS/INS segment
decoding feature, something that SVM does not have (yet ;-)
As I said in my mail, I doubt the usefulness of the shortcut in this
case, since it would require to access the guest memory and is used very
rarely. So for the sake of a saner implementation I would avoid
utilizing this feature, it simplifies the code much and avoids code
duplication. That's why my code just implements non-string instructions.
> One thing is: IIRC, old Intel CPUs don't supply the info, but your
> patch doesn't check that... so your patch can break the CPUs.
> Please refer to 15425.
But this is only true for the segment decoding part, right? Appendix G
of the Intel 3B manual only speaks of _this_ feature protected by bit 54
of IA32_VMX_BASIC MSR. Is the information shown in table 23-5 in section
23.2.1 not valid on all CPUs? If not, where can I check the support for
this?
Regards,
Andre.
--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 448-3567-12
next prev parent reply other threads:[~2010-03-31 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 8:47 [PATCH] x86/hvm: accelerate I/O intercept handling Andre Przywara
2010-03-31 9:26 ` Cui, Dexuan
2010-03-31 10:08 ` Andre Przywara [this message]
2010-04-01 5:15 ` Cui, Dexuan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BB31F08.20403@amd.com \
--to=andre.przywara@amd.com \
--cc=dexuan.cui@intel.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.