All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	"stefano.stabellini@eu.citrix.com"
	<stefano.stabellini@eu.citrix.com>
Subject: Re: [help]: handling IO instructions for hybrid
Date: Wed, 08 Feb 2012 19:18:45 -0800	[thread overview]
Message-ID: <CB587B15.2AB43%keir.xen@gmail.com> (raw)
In-Reply-To: <20120208181720.377bb098@mantra.us.oracle.com>

On 08/02/2012 18:17, "Mukesh Rathor" <mukesh.rathor@oracle.com> wrote:

> On Mon, 06 Feb 2012 19:41:23 +0000
> Keir Fraser <keir.xen@gmail.com> wrote:
> 
>> On 07/02/2012 02:26, "Mukesh Rathor" <mukesh.rathor@oracle.com> wrote:
>>> 
>>> I am figuring io access for hybrid guests, dom0 and domU. I see
>>> that there are two ways: PV -> emulate_privileged_op(), or hvm
>>> handles via handle_mmio()/handle_pio(). I am not familiar with
>>> either one, and would help me lot if anybody expert in that can
>>> suggest which way hybrid should go, both dom0 and domU. Any
>>> suggestions would help. If there are any docs on this, that would
>>> be great too.
>> 
>> Probably the PV route, for dom0 and domU. Really most things you want
>> to do, the PV route is going to be the right way (unless you are
>> PVHVM'ing certain things, e.g., like using EPT assistance for
>> pagetable handling).
>> 
>>  -- Keir
> 
> Thanks Keir. Just to confirm, the hybrid should continue to request
> iopl of 1, right?

I'm not sure it matters since the hybrid guest runs in ring 0 of non-root
context I believe? Since ring 1 is in that case unused, it doesn't matter
whether iopl is 0 or 1.

 -- Keir

      reply	other threads:[~2012-02-09  3:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07  2:26 [help]: handling IO instructions for hybrid Mukesh Rathor
2012-02-06 19:41 ` Keir Fraser
2012-02-09  2:17   ` Mukesh Rathor
2012-02-09  3:18     ` Keir Fraser [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=CB587B15.2AB43%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Xen-devel@lists.xensource.com \
    --cc=mukesh.rathor@oracle.com \
    --cc=stefano.stabellini@eu.citrix.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.