From: Sasha Levin <levinsasha928@gmail.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org, Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH] KVM: Implement support for the RH bit
Date: Thu, 01 Sep 2011 23:05:00 +0300 [thread overview]
Message-ID: <1314907500.3992.15.camel@lappy> (raw)
In-Reply-To: <20110901200303.GC26451@redhat.com>
On Thu, 2011-09-01 at 23:03 +0300, Gleb Natapov wrote:
> On Thu, Sep 01, 2011 at 10:58:31PM +0300, Sasha Levin wrote:
> > By "actual addressing model" I meant checking the ICR of of each APIC to
> > see if we should address it logically or physically.
> >
> This is definitely not what ICR of each APIC is about.
Thats what I understood from section 10.6.2 in the spec.
--
Sasha.
next prev parent reply other threads:[~2011-09-01 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 16:05 [PATCH] KVM: Implement support for the RH bit Sasha Levin
2011-09-01 17:45 ` Gleb Natapov
2011-09-01 18:59 ` Sasha Levin
2011-09-01 19:31 ` Gleb Natapov
2011-09-01 19:58 ` Sasha Levin
2011-09-01 20:03 ` Gleb Natapov
2011-09-01 20:05 ` Sasha Levin [this message]
2011-09-01 20:19 ` Gleb Natapov
2011-09-01 20:24 ` Sasha Levin
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=1314907500.3992.15.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--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