public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
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 18:27:44 +0200	[thread overview]
Message-ID: <4F257380.1030108@redhat.com> (raw)
In-Reply-To: <4F256BF2.1010906@web.de>

On 01/29/2012 05:55 PM, Jan Kiszka wrote:
> On 2012-01-29 16:52, Avi Kivity wrote:
> > 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.
>
> Possibly.
>
> What about that major/minor version entries in the KPCR? Do they work,
> and do we have a list of what should be there?

We don't.  But things like the IDT/GTD/TSS and especially SelfPcr look
like good candidates.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2012-01-29 16:27 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
2012-01-29 15:55     ` Jan Kiszka
2012-01-29 16:27       ` Avi Kivity [this message]
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=4F257380.1030108@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