All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Wu, Feng" <feng.wu@intel.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
	"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
	"Dong, Eddie" <eddie.dong@intel.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Jan Beulich <JBeulich@suse.com>,
	"Nakajima, Jun" <jun.nakajima@intel.com>
Subject: Re: [PATCH v3 4/9] Clear AC bit in RFLAGS to protect Xen itself by SMAP
Date: Tue, 29 Apr 2014 11:31:47 +0100	[thread overview]
Message-ID: <535F7F93.5090705@citrix.com> (raw)
In-Reply-To: <E959C4978C3B6342920538CF579893F001F4D792@SHSMSX104.ccr.corp.intel.com>

On 29/04/14 11:29, Wu, Feng wrote:
>
>> -----Original Message-----
>> From: Jan Beulich [mailto:JBeulich@suse.com]
>> Sent: Tuesday, April 29, 2014 5:48 PM
>> To: Wu, Feng
>> Cc: andrew.cooper3@citrix.com; ian.campbell@citrix.com; Dong, Eddie;
>> Nakajima, Jun; Tian, Kevin; xen-devel@lists.xen.org
>> Subject: RE: [PATCH v3 4/9] Clear AC bit in RFLAGS to protect Xen itself by SMAP
>>
>>>>> On 29.04.14 at 11:27, <feng.wu@intel.com> wrote:
>>> May I move the definition of SAVE_ALL (or more related code, such as,
>>> SAVE_VOLATILE, etc.) from " xen/include/asm-x86/x86_64/asm_defns.h " to "
>>> xen/include/asm-x86/asm_defns.h ", since I got an build error after adding a
>>> parameter to marco SAVE_ALL like this, which makes me think it should be
>>> defined after ASM_CLAC?
>> No problem (and in fact I wouldn't mind you merging all of
>> x86_64/asm_defns.h into the other file - that due at some point
>> anyway), but I'm afraid we'd want this to be yet another separate
>> prerequisite patch - not sure if you're up to that, or if you wouldn't
>> find it simpler to keep SAVE_ALL being a C macro then.
> I am fine with the merging task. But Is there anything hard to handle while merging x86_64/asm_defns.h to asm_defns.h, I am wondering
> why x86_64/asm_defns.h is there for a long time.

Because x86_32/asm_defns.h used to exist when we supported building Xen
as 32bit.  I wouldn't have thought there is anything problematic to be
encountered while merging the files.

~Andrew

  reply	other threads:[~2014-04-29 10:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28  3:15 [PATCH v3 4/9] Clear AC bit in RFLAGS to protect Xen itself by SMAP Feng Wu
2014-04-28  9:25 ` Jan Beulich
2014-04-28  9:43   ` Wu, Feng
2014-04-28  9:58     ` Jan Beulich
2014-04-29  3:06       ` Wu, Feng
2014-04-29  7:21         ` Jan Beulich
2014-04-29  8:19           ` Wu, Feng
2014-04-29  8:58             ` Jan Beulich
2014-04-29  9:27               ` Wu, Feng
2014-04-29  9:47                 ` Jan Beulich
2014-04-29 10:29                   ` Wu, Feng
2014-04-29 10:31                     ` Andrew Cooper [this message]
2014-04-29 10:35                       ` Wu, Feng
2014-04-29 10:42                     ` Jan Beulich
2014-04-29 10:49                       ` Wu, Feng
2014-04-29 11:53                         ` Jan Beulich

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=535F7F93.5090705@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=eddie.dong@intel.com \
    --cc=feng.wu@intel.com \
    --cc=ian.campbell@citrix.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.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 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.