public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Yang, Sheng" <sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH][Rebased LAPIC5] Reading PPR directly from function rather than apic page
Date: Tue, 21 Aug 2007 15:37:03 +0300	[thread overview]
Message-ID: <46CADC6F.8060708@qumranet.com> (raw)
In-Reply-To: <DB3BD37E3533EE46BED2FBA80995557F7056AC-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>

Yang, Sheng wrote:
> After introducing TPR shadow, many TPR change won't cause vmexit, so the
> present method of updating PPR can't catch it. Though we can also update
> PPR
> everytime when we want to read PPR, it's somehow ugly.
>
> Because there are only two places need reading PPR, and PPR is
> read-only, we
> do it in more clear way. Now the apic_update_PPR() have been replaced by
> apic_get_PPR() which returned current PPR, and we read the PPR directly
> from
> the function when we need it, rather than reading from apic page.
>
> Signed-off-by: Sheng Yang <sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
>
> Notice: This patch based on the rebased lapic5, for the current lapic5
> is broken...
>   

Patch is okay; pending only on the previous patch.

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


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

  parent reply	other threads:[~2007-08-21 12:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-21  6:23 [PATCH][Rebased LAPIC5] Reading PPR directly from function rather than apic page Yang, Sheng
     [not found] ` <DB3BD37E3533EE46BED2FBA80995557F7056AC-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-08-21 12:37   ` Avi Kivity [this message]
     [not found]     ` <46CADC6F.8060708-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-22  7:56       ` Yang, Sheng

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=46CADC6F.8060708@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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