All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Kevin Tian <kevin.tian@intel.com>, "keir@xen.org" <keir@xen.org>,
	"jinsong.liu@alibaba-inc.com" <jinsong.liu@alibaba-inc.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
	Yang Z Zhang <yang.z.zhang@intel.com>
Subject: Re: [PATCH 2/3] xen/vt-d: mask interrupt message generation
Date: Mon, 04 May 2015 19:21:14 +0800	[thread overview]
Message-ID: <5547562A.1040101@intel.com> (raw)
In-Reply-To: <554750860200007800076341@mail.emea.novell.com>

On 2015/5/4 16:57, Jan Beulich wrote:
>>>> On 04.05.15 at 07:08, <tiejun.chen@intel.com> wrote:
>> At first I doubted this is issued by some improper cache behaviors.
>> Because as you see, "root_entry[0] = 80f5001" indicates we already set
>> that present bit. But Caching Mode bit is zero in BDW so this means
>> remapping hardware doesn't own contest cache. And I also check xen
>> always calls clflush to write back memory on CPU side. (Even I also
>> tried to use wbinvd to replace clflush). And plus, you can see this
>> guest fault address is a weird zero, so I turned to concern if this is
>> just an unexpected fault which is pending because of some BIOS cleanup,
>> or undefined hardware behaviors. Here I mean clear_fault_bits() is
>> already not enough to clear this kind of pending interrupt before we
>> complete all VT-D initializations.
>
> This last aspect in particular needs more explanation, but I'm
> wary of the change in general (see Yang's response).
>

Sure.

As we discussed offline, Yang though at most this is a way to workaround 
our problem. So I would ping BIOS team to double check if this is an 
issue specific to some given BIOSs or platforms since this doesn't meet 
the current specification

Thanks
Tiejun

  reply	other threads:[~2015-05-04 11:21 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04  2:16 [PATCH 1/3] xen/vt-d: need barriers to workaround CLFLUSH Tiejun Chen
2015-05-04  2:16 ` [PATCH 2/3] xen/vt-d: mask interrupt message generation Tiejun Chen
2015-05-04  4:07   ` Zhang, Yang Z
2015-05-04  5:08     ` Chen, Tiejun
2015-05-04  6:41       ` Zhang, Yang Z
2015-05-04  8:57       ` Jan Beulich
2015-05-04 11:21         ` Chen, Tiejun [this message]
2015-05-04  2:16 ` [PATCH 3/3] xen/iommu: disable IOMMU engine completely before enter S5 Tiejun Chen
2015-05-04  9:00   ` Jan Beulich
2015-05-04  4:07 ` [PATCH 1/3] xen/vt-d: need barriers to workaround CLFLUSH Zhang, Yang Z
2015-05-04  8:52 ` Jan Beulich
2015-05-04  9:14   ` Andrew Cooper
2015-05-04  9:24     ` Jan Beulich
2015-05-05  1:13       ` Zhang, Yang Z
2015-05-05 15:46     ` Boris Ostrovsky
2015-05-05 15:58       ` Jan Beulich
2015-05-05 16:11         ` Boris Ostrovsky
2015-05-06  7:12           ` Jan Beulich
2015-05-06  7:26             ` Chen, Tiejun
2015-05-06  7:33               ` Jan Beulich
2015-05-06 15:11             ` Boris Ostrovsky
2015-05-06  7:09       ` Chen, Tiejun
2015-05-04 10:39   ` Chen, Tiejun
2015-05-04 10:43     ` Jan Beulich
2015-05-04 10:52       ` Tian, Kevin
2015-05-04 11:26         ` Chen, Tiejun
2015-05-05  1:13           ` Tian, Kevin
2015-05-05  2:45       ` Chen, Tiejun
2015-05-05  9:24         ` Jan Beulich
2015-05-06  6:47           ` Chen, Tiejun
2015-05-06  7:14             ` Jan Beulich
2015-05-04 15:22     ` Konrad Rzeszutek Wilk
2015-05-04 15:33       ` Andrew Cooper

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=5547562A.1040101@intel.com \
    --to=tiejun.chen@intel.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jinsong.liu@alibaba-inc.com \
    --cc=keir@xen.org \
    --cc=kevin.tian@intel.com \
    --cc=xen-devel@lists.xen.org \
    --cc=yang.z.zhang@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.