xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Tim Deegan <tim@xen.org>
Cc: "Keir (Xen.org)" <keir@xen.org>,
	"wei.huang2@amd.com" <wei.huang2@amd.com>,
	xen-devel <xen-devel@lists.xen.org>,
	Jan Beulich <JBeulich@suse.com>,
	"weiwang.dd@gmail.com" <weiwang.dd@gmail.com>,
	"xiantao.zhang@intel.com" <xiantao.zhang@intel.com>
Subject: Re: [PATCH] IOMMU: don't disable bus mastering on faults for devices used by Xen or Dom0
Date: Tue, 6 Nov 2012 15:16:50 +0100	[thread overview]
Message-ID: <1352211410.2155.7.camel@Solace> (raw)
In-Reply-To: <20121106135842.GB45690@ocelot.phlegethon.org>


[-- Attachment #1.1: Type: text/plain, Size: 1365 bytes --]

On Tue, 2012-11-06 at 13:58 +0000, Tim Deegan wrote:
> > It helps keeping Xen alive, but doesn't for any specific domain
> > (including Dom0).
> 
> Indeed.  (Intel) IOMMU interrupts are suppressed until the softirq
> handler acknowledges the error, but if the softirq handler doesn't
> disable the device, it will take another IOMMU interrupt immediately.
>
Right. I wasn't considering the possibility of this 'back-to-back'
variant of the thing.

> I thought the AMD side behaved eth same but clearly not -- I'll try to
> take a look at that later in the week.
> 
I think it does, or at least, I'm quite sure when I moved the fault
handling code in softiq context, I did it so that behavior was
consistent wrt both Intel and AMD (by explicitly silencing interrupts
until within the tasklet), at least for faults.

PPR came later and I moved them within the softirq as well after asking
AMD people, without having the possibility to test that myself.

So, to recap, feel free to check. Faults should behave as you're
describing, PPR I'm not sure. :-)

Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2012-11-06 14:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05 16:53 [PATCH] IOMMU: don't disable bus mastering on faults for devices used by Xen or Dom0 Jan Beulich
2012-11-05 17:15 ` Keir Fraser
2012-11-06  9:08   ` Jan Beulich
2012-11-06  9:44     ` Tim Deegan
2012-11-06 10:19       ` Jan Beulich
2012-11-06 12:08         ` Dario Faggioli
2012-11-06 12:38           ` Jan Beulich
2012-11-06 12:06       ` Dario Faggioli
2012-11-06 12:51         ` Jan Beulich
2012-11-06 13:58           ` Tim Deegan
2012-11-06 14:16             ` Dario Faggioli [this message]
2012-11-06 14:17             ` Jan Beulich
2012-11-06 14:29               ` Dario Faggioli
2012-11-08 12:42                 ` Tim Deegan
2012-11-06 14:24           ` Dario Faggioli
2012-11-07 16:05       ` [PATCH, v2] IOMMU: don't immediately disable bus mastering on faults Jan Beulich
2012-11-08 12:46         ` Tim Deegan
2012-11-08 13:46           ` Jan Beulich
2012-11-08 14:23             ` Tim Deegan
2012-11-08 18:07         ` Dario Faggioli
2012-11-30  9:42 ` [PATCH] IOMMU: don't disable bus mastering on faults for devices used by Xen or Dom0 Keir Fraser
2012-11-30  9:50   ` Jan Beulich
2012-12-03  6:08     ` Zhang, Xiantao
2012-12-03  7:36       ` Jan Beulich
2012-12-04  0:55         ` Zhang, Xiantao
2012-12-04  8:19           ` Jan Beulich

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=1352211410.2155.7.camel@Solace \
    --to=dario.faggioli@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --cc=tim@xen.org \
    --cc=wei.huang2@amd.com \
    --cc=weiwang.dd@gmail.com \
    --cc=xen-devel@lists.xen.org \
    --cc=xiantao.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).