From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: [PATCH 2/2] mwait_idle: Broadwell support Date: Thu, 16 Oct 2014 15:06:00 +0100 Message-ID: <543FECE8020000780003F43A@mail.emea.novell.com> References: <1410180127-4812-1-git-send-email-ross.lagerwall@citrix.com> <1410180127-4812-2-git-send-email-ross.lagerwall@citrix.com> <543FC00C.3050708@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <543FC00C.3050708@intel.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Tiejun Chen Cc: Ross Lagerwall , Xen-devel , Keir Fraser , len.brown@intel.com List-Id: xen-devel@lists.xenproject.org >>> On 16.10.14 at 14:54, wrote: > Did you guys validate this in real machine? Or any potential side affect? > > When I do IGD GFX passthrough with qemu-xen-traditional, I found in the > boot phase of VM, the target will reboot. After I revert this everything > is fine. Please be more precise. What is "target" here? Host? Guest? Also, reporting issues just verbally (i.e. without any logs or other actual technical information) rarely makes a lot of sense. > Note I don't add anything into codes. Here I just build Xen unstable 4.5 > to use qemu-xen-traditional. And additionally, my BDW is based on > stepping E, and guest is WindXP. But the change is only about C-state handling for a particular CPU model. There's really nothing being added that doesn't already work fine elsewhere. I.e. this patch being the apparent culprit of a problem you see makes it relatively likely that your hardware is having some issue. Jan