From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: konrad.wilk@oracle.com, Xen-devel@lists.xensource.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V0] linux PVH: Set CR4 flags
Date: Thu, 30 Jan 2014 15:31:44 -0800 [thread overview]
Message-ID: <20140130153144.10d6f91e@mantra.us.oracle.com> (raw)
In-Reply-To: <52EA3A3C.4030209@citrix.com>
On Thu, 30 Jan 2014 11:40:44 +0000
Roger Pau Monné <roger.pau@citrix.com> wrote:
> On 30/01/14 00:15, Mukesh Rathor wrote:
> > Konrad,
> >
> > The CR4 settings were dropped from my earlier patch because you
> > didn't wanna enable them. But since you do now, we need to set them
> > in the APs also. If you decide not too again, please apply my prev
> > patch "pvh: disable pse feature for now".
>
> Hello Mukesh,
>
> Could you push your CR related patches to a git repo branch? I'm
> currently having a bit of a mess in figuring out which ones should be
> applied and in which order.
>
> Thanks, Roger.
Hey Roger,
Unfortunately, I don't have them in a tree because my first patch was
changed during merge, and also the tree was refreshed. Basically, the end
result, we leave features enabled on linux side, thus setting not only
the cr0 bits, but also the cr4 PSE and PGE for APs (they were already
set for the BSP).
Konrad only merged the CR0 setting part of my first patch, hence this
patch to set the CR4 bits. Hope that makes sense. My latest tree is:
http://oss.us.oracle.com/git/mrathor/linux.git muk2
thanks
mukesh
prev parent reply other threads:[~2014-01-30 23:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 0:15 [PATCH V0] linux PVH: Set CR4 flags Mukesh Rathor
2014-01-30 0:15 ` [PATCH] pvh: set cr4 flags for APs Mukesh Rathor
2014-02-03 11:49 ` Konrad Rzeszutek Wilk
2014-02-03 19:30 ` Mukesh Rathor
2014-02-03 19:52 ` Konrad Rzeszutek Wilk
2014-02-03 20:43 ` Konrad Rzeszutek Wilk
2014-02-03 20:51 ` Mukesh Rathor
2014-01-30 11:40 ` [PATCH V0] linux PVH: Set CR4 flags Roger Pau Monné
2014-01-30 23:31 ` Mukesh Rathor [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=20140130153144.10d6f91e@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=Xen-devel@lists.xensource.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.pau@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 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).