From owner-freebsd-xen@FreeBSD.ORG Tue Sep 22 17:28:10 2009 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C632106566C for ; Tue, 22 Sep 2009 17:28:10 +0000 (UTC) (envelope-from toasty@dragondata.com) Received: from mail-iw0-f196.google.com (mail-iw0-f196.google.com [209.85.223.196]) by mx1.freebsd.org (Postfix) with ESMTP id 50FC08FC16 for ; Tue, 22 Sep 2009 17:28:10 +0000 (UTC) Received: by iwn34 with SMTP id 34so574686iwn.12 for ; Tue, 22 Sep 2009 10:28:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.83.75 with SMTP id e11mr2422853ibl.11.1253638985611; Tue, 22 Sep 2009 10:03:05 -0700 (PDT) X-Originating-IP: [67.186.84.206] In-Reply-To: <20090922131034.GV47688@deviant.kiev.zoral.com.ua> References: <20090922123401.GB29391@gta.com> <20090922131034.GV47688@deviant.kiev.zoral.com.ua> Date: Tue, 22 Sep 2009 12:03:05 -0500 Message-ID: <5078471e0909221003g43a125f4s99a1f841616bb184@mail.gmail.com> From: Kevin Day To: Kostik Belousov Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-xen@freebsd.org, Larry Baird Subject: Re: XEN 5.5.0 and clflush X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2009 17:28:10 -0000 On Tue, Sep 22, 2009 at 8:10 AM, Kostik Belousov wrote: > > I think I will have to disable CLFLUSH support for intel CPUs when > self-snoop > is not reported. > > That's the kinda weird part about this though... It's not triggering an Invalid Instruction, but a GPF. Looking at AMD's description of how CLFLUSH is supposed to work, I don't see why it's faulting with what looks like a valid address. While this is probably far outside the scope of what their entry-level support techs will understand, I can try raising this as a bug with Citrix under our support contract if you're confident that this is broken on Xen's end.