xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Juergen Gross <jgross@suse.com>
Cc: minios-devel@lists.xenproject.org,
	xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com>,
	samuel.thibault@ens-lyon.org
Subject: Re: [PATCH] minios: fix build issue with xen_*mb defines
Date: Wed, 28 Sep 2016 11:10:15 +0100	[thread overview]
Message-ID: <20160928101015.GR16004@citrix.com> (raw)
In-Reply-To: <e59337a4-2fc8-d924-07d9-3e40f04b7499@suse.com>

On Wed, Sep 28, 2016 at 12:06:02PM +0200, Juergen Gross wrote:
> On 28/09/16 12:01, Wei Liu wrote:
> > On Wed, Sep 28, 2016 at 11:50:04AM +0200, Juergen Gross wrote:
> >> Commit e35295d724d64e6e025ec31c2e510e448b8641d1 ("mini-os: fix builds
> >> with uncommon config settings") introduced a bug which will break
> >> the build, as xc_minios.c will have defined those macros via
> >> xc_private.h.
> >>
> >> Fix this by defining the macros only if compiling a minios source.
> >>
> > 
> > Reported-by: Wei Liu <wei.liu2@citrix.com>
> > 
> >> Signed-off-by: Juergen Gross <jgross@suse.com>
> > 
> > Reviewed-by: Wei Liu <wei.liu2@citrix.com>
> > 
> >> ---
> >>  include/x86/os.h | 4 ++--
> >>  1 file changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/include/x86/os.h b/include/x86/os.h
> >> index 0f5dd6c..fbc2eeb 100644
> >> --- a/include/x86/os.h
> >> +++ b/include/x86/os.h
> >> @@ -511,14 +511,14 @@ static __inline__ unsigned long __ffs(unsigned long word)
> >>  #error "Unsupported architecture"
> >>  #endif
> >>  
> >> -#endif /* ifdef __INSIDE_MINIOS */
> >> -
> >>  /********************* common i386 and x86_64  ****************************/
> > 
> > One nit, might want to retain the position of this comment.
> 
> Didn't I?
> 
> Or do you mean it should be outside the ifdef? So keeping the #endif
> above and adding another #ifdef __INSIDE_MINIOS after the comment?
> 

What I meant is to have the comment before wrmsr as before. But I think
it is also a valid comment in its position now. I don't want to bikeshed
too much on this.

Wei.

> > 
> >>  #define xen_mb()  mb()
> >>  #define xen_rmb() rmb()
> >>  #define xen_wmb() wmb()
> >>  #define xen_barrier() asm volatile ( "" : : : "memory")
> >>  
> >> +#endif /* ifdef __INSIDE_MINIOS */
> >> +
> >>  #define wrmsr(msr,val1,val2) \
> >>        __asm__ __volatile__("wrmsr" \
> >>                             : /* no outputs */ \
> >> -- 
> >> 2.6.6
> >>
> > 
> 

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

  reply	other threads:[~2016-09-28 10:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-28  9:50 [PATCH] minios: fix build issue with xen_*mb defines Juergen Gross
2016-09-28 10:01 ` Wei Liu
2016-09-28 10:06   ` Juergen Gross
2016-09-28 10:10     ` Wei Liu [this message]
2016-09-28 10:14       ` [Minios-devel] " Juergen Gross
2016-09-28 11:07 ` Samuel Thibault
2016-09-28 11:10   ` [Minios-devel] " Wei Liu

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=20160928101015.GR16004@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=jgross@suse.com \
    --cc=minios-devel@lists.xenproject.org \
    --cc=samuel.thibault@ens-lyon.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 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).