From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Gleb Natapov <gleb@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: kvm's vapic
Date: Sun, 29 Jan 2012 17:52:45 +0200 [thread overview]
Message-ID: <4F256B4D.4080501@redhat.com> (raw)
In-Reply-To: <4F256AF2.1090106@redhat.com>
On 01/29/2012 05:51 PM, Avi Kivity wrote:
> > Already the assumption that we find a CPU index at
> > fs:0x51 is apparently hard-coding this. Or that kernel code is at
> > 0x8xxxxxxx or 0xExxxxxxx.
> >
> > But what makes sure that we aren't patching some other obscure OS that
> > doesn't comply with our assumptions but triggers the TPR access reports
> > nevertheless?
>
> Not much, but we've never had an issue.
Checking that the bios is mapped at 0x[8e]0000000 + phys should filter
out most non-Windows OSes.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-01-29 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 15:37 kvm's vapic Jan Kiszka
2012-01-29 15:51 ` Avi Kivity
2012-01-29 15:52 ` Avi Kivity [this message]
2012-01-29 15:55 ` Jan Kiszka
2012-01-29 16:27 ` Avi Kivity
2012-01-29 16:31 ` Jan Kiszka
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=4F256B4D.4080501@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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