From: "H. Peter Anvin" <hpa@zytor.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Avi Kivity <avi@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kvm: optimize ISR lookups
Date: Wed, 23 May 2012 12:25:50 -0700 [thread overview]
Message-ID: <4FBD39BE.8040101@zytor.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1205232037220.3231@ionos>
On 05/23/2012 11:37 AM, Thomas Gleixner wrote:
>>
>> That works, but replaces one problem with another: now we have two
>> sources for the same data, and need to juggle between them depending on
>> register number (either synchronizing in both directions, or special
>> casing); so you're simplifying one thing at the expense of the other.
>> If the microcode starts accessing more registers, then having two
>> layouts becomes even uglier.
>
> Fair enough :)
Yes, the µcode accessing this data structure directly probably falls
under the category of a legitimate need to stick to the hardware format.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-05-23 19:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 16:37 [PATCH] kvm: optimize ISR lookups Michael S. Tsirkin
2012-05-21 18:44 ` Michael S. Tsirkin
2012-05-21 21:04 ` Thomas Gleixner
2012-05-21 21:51 ` Michael S. Tsirkin
2012-05-21 22:14 ` Thomas Gleixner
2012-05-21 22:24 ` Michael S. Tsirkin
2012-05-21 22:44 ` Thomas Gleixner
2012-05-21 22:50 ` Michael S. Tsirkin
2012-05-21 23:01 ` Thomas Gleixner
2012-05-22 10:46 ` Avi Kivity
2012-05-23 14:48 ` Ingo Molnar
2012-05-23 15:03 ` Avi Kivity
2012-05-23 20:10 ` Thomas Gleixner
2012-05-23 20:46 ` Michael S. Tsirkin
2012-05-23 23:02 ` Thomas Gleixner
2012-05-23 15:14 ` Michael S. Tsirkin
2012-05-23 19:22 ` H. Peter Anvin
2012-05-21 23:11 ` Thomas Gleixner
2012-05-21 23:06 ` Michael S. Tsirkin
2012-05-21 23:12 ` H. Peter Anvin
2012-05-21 23:36 ` Thomas Gleixner
2012-05-22 10:59 ` Avi Kivity
2012-05-22 17:26 ` Thomas Gleixner
2012-05-23 15:10 ` Avi Kivity
2012-05-23 18:37 ` Thomas Gleixner
2012-05-23 19:25 ` H. Peter Anvin [this message]
2012-05-23 22:00 ` Thomas Gleixner
2012-05-30 14:18 ` 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:
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=4FBD39BE.8040101@zytor.com \
--to=hpa@zytor.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).