All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>
Cc: xen-devel@lists.xenproject.org, Keir Fraser <keir@xen.org>,
	Tim Deegan <tim@xen.org>, Jan Beulich <JBeulich@suse.com>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH RFC v2] pvh: clearly specify used parameters in vcpu_guest_context
Date: Tue, 19 Nov 2013 11:11:47 +0000	[thread overview]
Message-ID: <528B4773.2020806@eu.citrix.com> (raw)
In-Reply-To: <20131118143015.14becc57@mantra.us.oracle.com>

On 11/18/2013 10:30 PM, Mukesh Rathor wrote:
> On Mon, 18 Nov 2013 19:18:31 +0100
> Roger Pau Monne <roger.pau@citrix.com> wrote:
>
>> The aim of this patch is to define a stable way in which PVH is
>> going to do AP bringup.
>>
>> Since we are running inside of a HVM container, PVH should only need
>> to set flags, cr3 and user_regs in order to bring up a vCPU, the rest
>> can be set once the vCPU is started using the bare metal methods.
>> Additionally, the guest can also set cr0 and cr4, and those values
>> will be appended to the default values set by Xen.
>>
>> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
>
> OK from linux perspective. Tested. If non-maintainers are
> allowed to ack:
>
> Acked-by: Mukesh Rathor <mukesh.rathor@oracle.com>

I think for this code your opinion definitely matters. :-)

Thanks,
  -George

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-11-19 11:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 18:18 [PATCH RFC v2] pvh: clearly specify used parameters in vcpu_guest_context Roger Pau Monne
2013-11-18 22:30 ` Mukesh Rathor
2013-11-19 11:11   ` George Dunlap [this message]
2013-11-19 10:34 ` George Dunlap
2013-11-19 10:42   ` Roger Pau Monné
2013-11-19 11:10     ` George Dunlap
2013-11-19 10:44   ` Roger Pau Monné

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=528B4773.2020806@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --cc=mukesh.rathor@oracle.com \
    --cc=roger.pau@citrix.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 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.