From: Eduardo Habkost <ehabkost@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
x86@kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Chris Wright <chrisw@sous-sol.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Alok Kataria <akataria@vmware.com>
Subject: Re: [PATCH] x86, paravirt: BUG_ON on {rd,wr}msr exceptions
Date: Mon, 28 Jul 2014 17:39:55 -0300 [thread overview]
Message-ID: <20140728203955.GA4611@thinpad.lan.raisama.net> (raw)
In-Reply-To: <53D6A1F2.5070404@zytor.com>
On Mon, Jul 28, 2014 at 12:18:10PM -0700, H. Peter Anvin wrote:
> On 07/28/2014 12:04 PM, Eduardo Habkost wrote:
> > When CONFIG_PARAVIRT is enabled, the kernel is ignoring exceptions on
> > the {rd,wr}msr instructions. This makes serious issues (either on the
> > guest kernel, or on the host) be silently ignored, and is different from
> > the native MSR code (which does not ignore the exceptions).
> >
> > As paravirt.h already includes linux/bug.h, I don't see what was the
> > original issue preventing BUG_ON from being used.
> >
> > Change rdmsr(), wrmsr(), and rdmsrl() to BUG_ON() on errors.
>
> How much does this bloat the kernel?
It seems to add 8 bytes to each {wr,rd}msr() call (4 extra instructions:
test, jmp, ud2, jmp).
allyesconfig, paravirt enabled, before:
text data bss dec hex filename
108368312 23500872 55705600 187574784 b2e2a00 vmlinux
allyesconfig, paravirt enabled, after:
text data bss dec hex filename
108384438 23500904 55717888 187603230 b2e991e vmlinux
allyesconfig vmlinux is 28446 bytes larger.
An alternative is to add read_msr_unsafe() & write_msr_unsafe() fields
to pv_cpu_ops, pointing to native_read_msr() & native_write_msr().
--
Eduardo
next prev parent reply other threads:[~2014-07-28 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 19:04 [PATCH] x86, paravirt: BUG_ON on {rd,wr}msr exceptions Eduardo Habkost
2014-07-28 19:18 ` H. Peter Anvin
2014-07-28 20:39 ` Eduardo Habkost [this message]
2014-07-28 20:43 ` H. Peter Anvin
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=20140728203955.GA4611@thinpad.lan.raisama.net \
--to=ehabkost@redhat.com \
--cc=akataria@vmware.com \
--cc=chrisw@sous-sol.org \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@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