From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "He, Qing" <qing.he-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Reverting back in lapic2 branch of kvm-userspace?
Date: Tue, 24 Jul 2007 08:48:55 +0300 [thread overview]
Message-ID: <46A592C7.7020604@qumranet.com> (raw)
In-Reply-To: <37E52D09333DE2469A03574C88DBF40F048EA4-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
He, Qing wrote:
> Avi/Eddie,
> I just noticed that the latest commit in lapic2 branch of
> kvm-userspace effectively disabled in-kernel apic and ioapic. I don't
> suppose it's intended, is it?
>
>
It was a mistake on my part. I re-did the commit and pushed a new
version (you need to fetch with +lapic2).
Eddie, hopefully there aren't more mistakes like that, can you check?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
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-07-24 5:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 5:23 Reverting back in lapic2 branch of kvm-userspace? He, Qing
[not found] ` <37E52D09333DE2469A03574C88DBF40F048EA4-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-07-24 5:48 ` Avi Kivity [this message]
[not found] ` <46A592C7.7020604-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-24 5:54 ` Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A01D15BBE-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-07-24 6:02 ` Avi Kivity
[not found] ` <46A59610.7080206-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-24 6:51 ` Dong, Eddie
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=46A592C7.7020604@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=qing.he-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