From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Jeremy Fitzhardinge <jeremy@xensource.com>,
Chris Wright <chrisw@sous-sol.org>,
Alok Kataria <akataria@vmware.com>,
Rusty Russell <rusty@rustcorp.com.au>,
virtualization@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] paravirt: noreplace-paravirt is implemented for x86 and ia-64
Date: Wed, 11 Aug 2010 09:42:49 -0700 [thread overview]
Message-ID: <4C62D309.5010909@goop.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1008111832510.2702@pobox.suse.cz>
On 08/11/2010 09:34 AM, Jiri Kosina wrote:
> kernel-parameters.txt lists 'noreplace-paravirt' parameter as being
> limited to X86-32, which is incorrect -- it's actually supported by
> x86-32, x86-64 and ia-64.
>
> Signed-off-by: Jiri Kosina<jkosina@suse.cz>
Acked-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> ---
> Documentation/kernel-parameters.txt | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> index d529b13..8ed3a77 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -1777,7 +1777,7 @@ and is between 256 and 4096 characters. It is defined in the file
> norandmaps Don't use address space randomization. Equivalent to
> echo 0> /proc/sys/kernel/randomize_va_space
>
> - noreplace-paravirt [X86-32,PV_OPS] Don't patch paravirt_ops
> + noreplace-paravirt [X86,IA-64,PV_OPS] Don't patch paravirt_ops
>
> noreplace-smp [X86-32,SMP] Don't replace SMP instructions
> with UP alternatives
next prev parent reply other threads:[~2010-08-11 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 16:34 [PATCH] paravirt: noreplace-paravirt is implemented for x86 and ia-64 Jiri Kosina
2010-08-11 16:42 ` Jeremy Fitzhardinge [this message]
2010-08-16 13:04 ` Jiri Kosina
2010-08-16 19:40 ` Jeremy Fitzhardinge
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=4C62D309.5010909@goop.org \
--to=jeremy@goop.org \
--cc=akataria@vmware.com \
--cc=chrisw@sous-sol.org \
--cc=jeremy@xensource.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.osdl.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.