LKML Archive on
help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <>
To: Rusty Russell <>
Cc: Avi Kivity <>, Andrew Morton <>,
	lkml - Kernel Mailing List <>,
	Andi Kleen <>
Subject: Re: [PATCH] Cleanup: rationalize paravirt wrappers
Date: Thu, 22 Mar 2007 01:09:32 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <1174550442.2713.128.camel@localhost.localdomain>

Rusty Russell wrote:
> The behaviour change (don't oops when an invalid rdmsr is used) was
> there with CONFIG_PARAVIRT=y, the cleanup just made !CONFIG_PARAVIRT the
> same.  Is it important?

We could always fling a BUG_ON in the non-safe versions, which would
probably be more informative than a GPF or whatever a bad MSR gives you.


  reply	other threads:[~2007-03-22  8:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22  2:41 Rusty Russell
2007-03-22  7:30 ` Avi Kivity
2007-03-22  8:00   ` Rusty Russell
2007-03-22  8:09     ` Jeremy Fitzhardinge [this message]
2007-03-22  8:09     ` Avi Kivity
2007-03-22  9:55       ` Rusty Russell
2007-03-23 11:05 ` Rusty Russell
2007-03-23 11:19   ` Avi Kivity

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] Cleanup: rationalize paravirt wrappers' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).