From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Kevin Tian <kevin.tian@intel.com>,
Eddie Dong <eddie.dong@intel.com>,
Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: [PATCH v2] VMX: don't allow PVH to reach handle_mmio()
Date: Tue, 9 Dec 2014 18:01:54 +0100 [thread overview]
Message-ID: <54872B02.50300@citrix.com> (raw)
In-Reply-To: <54857995020000780004DA2D@mail.emea.novell.com>
El 08/12/14 a les 10.12, Jan Beulich ha escrit:
> PVH guests accessing I/O ports via string ops is not supported yet.
>
> Reported-by: Roger Pau Monné<roger.pau@citrix.com>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
This looks fine to me (at least it doesn't break the existing IN/OUT
users), and seems the best solution 4.5 wise:
Acked-by: Roger Pau Monné <roger.pau@citrix.com>
For 4.6 I think we need to start using a different hvm_io_bitmap for PVH
Dom0 that allows direct access to the IO ports, bypassing the vmexit and
simplifying the code in Xen (this would also fix INS/OUTS). Still not
sure what should be done for PVH DomUs, specially when PVH gains support
for pci-passthrough.
Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-12-09 17:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 9:12 [PATCH v2] VMX: don't allow PVH to reach handle_mmio() Jan Beulich
2014-12-08 22:12 ` Mukesh Rathor
2014-12-09 17:01 ` Roger Pau Monné [this message]
2014-12-09 17:19 ` Jan Beulich
2014-12-09 17:49 ` Roger Pau Monné
2014-12-10 9:07 ` Jan Beulich
2014-12-10 17:08 ` Konrad Rzeszutek Wilk
2014-12-10 5:07 ` Tian, Kevin
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=54872B02.50300@citrix.com \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=eddie.dong@intel.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xenproject.org \
/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.