xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Tim Deegan <tim@xen.org>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: [PATCH] Re:  I/O port access handling for PVH
Date: Mon, 2 Dec 2013 11:31:02 +0000	[thread overview]
Message-ID: <529C6F76.5050205@eu.citrix.com> (raw)
In-Reply-To: <52986A150200007800108111@nat28.tlf.novell.com>

On 11/29/2013 09:19 AM, Jan Beulich wrote:
>>>> On 28.11.13 at 12:44, Tim Deegan <tim@xen.org> wrote:
>> At 11:37 +0000 on 28 Nov (1385635050), George Dunlap wrote:
>>> On 11/28/2013 11:01 AM, Tim Deegan wrote:
>>>> At 15:10 +0100 on 21 Oct (1382364606), Jan Beulich wrote:
>>>>> In particular it would then hopefully be safe to do all that without
>>>>> the on-stack emulation stub, as this ought to be necessary only
>>>>> for Dom0, which ought to always have direct access to such
>>>>> "special" I/O ports. With one apparent caveat: SVM sets
>>>>> GENERAL1_INTERCEPT_SMI (for a reason that escapes my right
>>>>> now), and hence control doesn't transfer directly to SMM when
>>>>> an SMI occurs (and consequently registers aren't expected). But
>>>>> I would hope that this intercept isn't really needed, and hence
>>>>> could be dropped at least for PVH guests.
>>>> (I realise I'm rather late replying to this - I put it aside and then
>>>> only found it again today)
>>>>
>>>> On machines where the BIOS has locked down SMM mode, this
>>>> intercept is in fact ignored by the hardware, and that works fine.
>>>> So we can drop it for all VMs if it's convenient:
>>>>
>>>> commit a842864f3901078e2a5f4d1cca2f01a72c8d7d13
>>>> Author: Tim Deegan <tim@xen.org>
>>>> Date:   Thu Nov 28 10:58:42 2013 +0000
>>>>
>>>>       x86/svm: don't intercept SMI.
>>>>       
>>>>       The SMI intercept is ignored anyway when the BIOS has set the SMMLOCK
>>>>       bit in HWCR (see APM v3.21, volume 2, 15.13.3) and it's convenient for
>>>>       PVH IO processing to have the SMI handled directly with the guest's
>>>>       GPR state (for BIOSes that use SMI as a sort of function call
>> interface).
>>>>       
>>>>       Signed-off-by: Tim Deegan <tim@xen.org>
>>> I take it you're not targeting this for 4.4?
>> Indeed not.  Sorry, I should have said so.
> And even more so considering that PVH support on SVM is going
> to remain a todo item for after 4.4 anyway.

Yes, I had started to write this, but figured there was no point 
discussing the merits of accepting it if Tim wasn't asking for it to be 
accepted. :-)

  -George

      reply	other threads:[~2013-12-02 11:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-21 14:10 I/O port access handling for PVH Jan Beulich
2013-11-28 11:01 ` [PATCH] " Tim Deegan
2013-11-28 11:37   ` George Dunlap
2013-11-28 11:44     ` Tim Deegan
2013-11-29  9:19       ` Jan Beulich
2013-12-02 11:31         ` George Dunlap [this message]

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=529C6F76.5050205@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=tim@xen.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).