public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Dong, Eddie" <eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Joerg.Roedel-5C7GfCeVMHo@public.gmane.org,
	Markus Rechberger
	<markus.rechberger-5C7GfCeVMHo@public.gmane.org>
Subject: Re: [PATCH] Fix writing back APIC reset to inkernel APIC
Date: Sun, 04 Nov 2007 09:49:39 +0200	[thread overview]
Message-ID: <472D7993.8010802@qumranet.com> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A0250DC9B-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 691 bytes --]

Dong, Eddie wrote:
> Yes, when reseting, we need to reset both APIC/PIC/IOAPIC and pv
> driver in future, and also VCPU.
> But isn't apic_reset a pure user level APIC thing?

The reset callbacks are still called, so the userspace apic is still reset.

> BTW
> I posted a patch to support kernel device reset which is still pending.
> And I think Avi has some idea to support too and is working on:-)

I'm supposed to be working on this, but instead I'm doing binary
patching hacks and travelling. I'll get back on this, though, this is
hurting.

I think the patch is good, will apply after testing it in smp a bit.


-- 
Any sufficiently difficult bug is indistinguishable from a feature.



[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

  parent reply	other threads:[~2007-11-04  7:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-01 15:35 [PATCH] Fix writing back APIC reset to inkernel APIC Markus Rechberger
     [not found] ` <4729F257.30502-5C7GfCeVMHo@public.gmane.org>
2007-11-01 23:02   ` Dor Laor
     [not found]     ` <472A5AF4.9040900-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-02  3:07       ` Dong, Eddie
     [not found]         ` <10EA09EFD8728347A513008B6B0DA77A0250DC9B-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-11-04  7:49           ` Avi Kivity [this message]
     [not found]             ` <472D7993.8010802-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-05  8:58               ` Dong, Eddie
     [not found]                 ` <10EA09EFD8728347A513008B6B0DA77A02557D4B-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-11-05 14:03                   ` Avi Kivity
2007-11-06 14:21   ` 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=472D7993.8010802@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=Joerg.Roedel-5C7GfCeVMHo@public.gmane.org \
    --cc=eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=markus.rechberger-5C7GfCeVMHo@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