xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [RFC PATCH 12/16]: PVH xen: return PVH features during creation, etc...
Date: Fri, 18 Jan 2013 12:41:02 -0800	[thread overview]
Message-ID: <20130118124102.33622f00@mantra.us.oracle.com> (raw)
In-Reply-To: <50F9228502000078000B7354@nat28.tlf.novell.com>

On Fri, 18 Jan 2013 09:23:01 +0000
"Jan Beulich" <JBeulich@suse.com> wrote:

> >>> On 18.01.13 at 03:29, Mukesh Rathor <mukesh.rathor@oracle.com>
> >>> wrote:
> > Done. No other callers of prop_page_fault for PVH. So are you OK
> > with something like this:
> > 
> > static noinline int vmxit_invalid_op(struct cpu_user_regs *regs)
> > {
> >     ulong addr=0;
> > 
> >     if ( guest_kernel_mode(current, regs) ||
> >          (addr = emulate_forced_invalid_op(regs)) == 0 )
> 
> Actually, on a second thought that depends on whether you want
> to be able to build kernels that can run both PV and PVH. If so,
> you may need to emulate this even for the guest kernel.

Actually, I changed linux code so that PVH paths will only go 
thru native_cpuid(). So we can leave this as is to discourage
future XEN_EMULATE_PREFIX. Sound good? In PV mode it will not be 
running in HVM container, hence not go thru this path.


> >     if ( is_pvh_vcpu(current) )
> >         regs->eip = eip;
> >     else
> >         instruction_done(regs, eip, 0);
> 
> Why can't you use instruction_done() (or make it fit your needs,
> so that other code wanting to use it wouldn't need similar special
> casing)?

Sure, NP. Done.

Thanks,
Mukesh

  reply	other threads:[~2013-01-18 20:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-12  2:07 [RFC PATCH 12/16]: PVH xen: return PVH features during creation, etc Mukesh Rathor
2013-01-14 12:20 ` Jan Beulich
2013-01-17 23:36   ` Mukesh Rathor
2013-01-18  2:29     ` Mukesh Rathor
2013-01-18  9:23       ` Jan Beulich
2013-01-18 20:41         ` Mukesh Rathor [this message]
2013-01-24 16:57 ` Tim Deegan
2013-01-25  2:08   ` Mukesh Rathor

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=20130118124102.33622f00@mantra.us.oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xen.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).