From: Paul Bolle <pebolle@tiscali.nl>
To: linux-ia64@vger.kernel.org
Subject: Re: ia64: CONFIG_PARAVIRT_GUEST_ASM_CLOBBER_CHECK?
Date: Thu, 22 May 2014 08:51:30 +0000 [thread overview]
Message-ID: <1400748690.16832.10.camel@x220> (raw)
In-Reply-To: <1400748416.16832.7.camel@x220>
Tony, Fenghua,
On Thu, 2014-05-22 at 10:46 +0200, Paul Bolle wrote:
> v2.6.27 shipped with commit e92e8c68a61a ("[IA64] pvops: define
> paravirtualized instructions for native."). That commit added a
> preprocessor test for CONFIG_PARAVIRT_GUEST_ASM_CLOBBER_CHECK to
> arch/ia64/include/asm/native/inst.h.
>
> There never was a Kconfig symbol PARAVIRT_GUEST_ASM_CLOBBER_CHECK, so
> this test has always evaluated to false.
>
> Was this macro intended to be set through the kconfig tools? Or was it
> perhaps intended to be set manually whenever one wanted to use it?
> Either way, is that macro and the code currently hidden behind it still
> needed?
Isaku's address bounces. So I'm not likely to get a reply from Isaku.
Could one of you please have a look at this?
Paul Bolle
next prev parent reply other threads:[~2014-05-22 8:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 8:46 ia64: CONFIG_PARAVIRT_GUEST_ASM_CLOBBER_CHECK? Paul Bolle
2014-05-22 8:51 ` Paul Bolle [this message]
2014-05-28 22:34 ` Luck, Tony
2014-05-28 22:46 ` Paul Bolle
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=1400748690.16832.10.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-ia64@vger.kernel.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