From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sheng Yang Subject: Re: [PATCH] KVM: Merge kvm_ioapic_get_delivery_bitmask into kvm_get_intr_delivery_bitmask Date: Wed, 4 Mar 2009 10:59:47 +0800 Message-ID: <200903041059.47652.sheng@linux.intel.com> References: <1235981973-6740-1-git-send-email-sheng@linux.intel.com> <200903041041.35016.sheng@linux.intel.com> <20090304025506.GA21902@amt.cnet> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: Avi Kivity , kvm@vger.kernel.org, Gleb Natapov To: Marcelo Tosatti Return-path: Received: from mga06.intel.com ([134.134.136.21]:10380 "EHLO orsmga101.jf.intel.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750867AbZCDC7x (ORCPT ); Tue, 3 Mar 2009 21:59:53 -0500 In-Reply-To: <20090304025506.GA21902@amt.cnet> Content-Disposition: inline Sender: kvm-owner@vger.kernel.org List-ID: On Wednesday 04 March 2009 10:55:06 Marcelo Tosatti wrote: > Hi Sheng, > > > > The spec says broadcast is not supported with lowest priority delivery > > > mode, and that "must not be configured by software". I wonder what > > > happens in HW if you do that. > > > > Um.. So you mean to prohibit this kind of action? OK. > > No, I'm just wondering what the HW does, and what are the implications > of the (supposedly) different behaviour KVM emulates. Well, no clue to how HW works... Maybe at least note this and warning guest is OK... > > > Unrelated question, what was the issue (in detail) which caused > > > this change again: > > > > I have dig out my old post (I thought you are also involved :) ) > > Short memory :) > > Thanks, will read tomorrow. :)