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] Enable TPR shadow on CR8 access
Date: Wed, 22 Aug 2007 11:32:29 +0300 [thread overview]
Message-ID: <46CBF49D.6090206@qumranet.com> (raw)
In-Reply-To: <DB3BD37E3533EE46BED2FBA80995557F705B18-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Yang, Sheng wrote:
>>
>> Wait, which lapic5 is broken and which is okay?!
>>
>> Can you explain? maybe post sha1 hashes?
>>
>>
>
> Sorry for not describe it clearly.
>
> The ordinary lapic5 branch is broken now, we can make, but running it
> would result in host crash(we mostly using module). Eddie found that if
> we rebase the lapic5, we can get it work. So that is what I mean Rebased
> LAPIC5.
>
Ah, understood. I will rebase and apply your patches.
--
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/
next prev parent reply other threads:[~2007-08-22 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 6:21 [PATCH][Rebased LAPIC5] Enable TPR shadow on CR8 access Yang, Sheng
[not found] ` <DB3BD37E3533EE46BED2FBA80995557F7056A8-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-08-21 12:34 ` Avi Kivity
[not found] ` <46CADBE7.4080400-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-22 7:47 ` Yang, Sheng
[not found] ` <DB3BD37E3533EE46BED2FBA80995557F705B18-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-08-22 8:32 ` Avi Kivity [this message]
2007-08-22 7:55 ` Yang, Sheng
[not found] ` <DB3BD37E3533EE46BED2FBA80995557F705B2B-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-08-22 12:03 ` 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=46CBF49D.6090206@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