From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=56733 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OVhLK-0007Zm-GL for qemu-devel@nongnu.org; Mon, 05 Jul 2010 04:47:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OVhLJ-0006N9-71 for qemu-devel@nongnu.org; Mon, 05 Jul 2010 04:47:58 -0400 Received: from mx1.redhat.com ([209.132.183.28]:54939) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OVhLJ-0006Mq-0Q for qemu-devel@nongnu.org; Mon, 05 Jul 2010 04:47:57 -0400 Message-ID: <4C319C30.30308@redhat.com> Date: Mon, 05 Jul 2010 11:47:44 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [Bug 599958] Re: Timedrift problems with Win7: hpet missing time drift fixups References: <20100629211802.16137.10587.malonedeb@soybean.canonical.com> <4C2EECE8.8030305@web.de> <201007042306.57852.paul@codesourcery.com> <4C317E2A.7090101@web.de> <20100705064239.GI4689@redhat.com> <4C31807B.2030401@web.de> <20100705070017.GJ4689@redhat.com> <4C318B74.3040403@web.de> In-Reply-To: <4C318B74.3040403@web.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Blue Swirl , Paul Brook , Gleb Natapov , qemu-devel@nongnu.org On 07/05/2010 10:36 AM, Jan Kiszka wrote: > >> Assumes that CPU with >> lowest index is BSP (that one we can actually guaranty if we want >> to). >> > Well, the generic solution would be returning a bitmap of the CPUs that > were affected, but this is impractical. However, at least x86 should be > fine with the information "state change also on BSP", e.g. like this: > 0 - state change on one or more CPUs, none of them is the BSP > 1 - state change on BSP (and possible more CPUs) > What about ack notifiers? Ask the APIC to notify you when an interrupt is acked. That allows you to track the BSP, all cpus, or some subset. Masking can be seen at the irq controller level. It's more involved, but provides more information. -- error compiling committee.c: too many arguments to function