From: Dario Faggioli <raistlin@linux.it>
To: Keir Fraser <keir@xen.org>
Cc: Wei Wang2 <wei.wang2@amd.com>,
"allen.m.kay@intel.com" <allen.m.kay@intel.com>,
xen-devel@lists.xensource.com, Tim Deegan <tim@xen.org>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCHv2 2 of 2] Move IOMMU faults handling into softirq for AMD-Vi.
Date: Wed, 18 Jan 2012 09:53:20 +0100 [thread overview]
Message-ID: <1326876800.2375.18.camel@Abyss> (raw)
In-Reply-To: <CB3B094F.379B1%keir@xen.org>
[-- Attachment #1.1: Type: text/plain, Size: 1578 bytes --]
On Tue, 2012-01-17 at 11:17 +0000, Keir Fraser wrote:
> > Dealing with interrupts from AMD-Vi IOMMU(s) is deferred to a softirq-tasklet,
> > raised by the actual IRQ handler. To avoid more interrupts being generated
> > (because of further faults), they must be masked in the IOMMU within the low
> > level IRQ handler and enabled back in the tasklet body. Notice that this may
> > cause the log to overflow, but none of the existing entry will be overwritten.
> >
> > Signed-off-by: Dario Faggioli <dario.faggioli@citrix.com>
>
> This patch needs fixing to apply to xen-unstable tip. Please do that and
> resubmit.
>
I see. I can easily rebase the patch but there are functional changes
involved, so I'd like to know what you think it's best to do first.
In particular, the clash is against Wei's patches introducing PPR. So
now the IOMMU interrupt handler checks both event log and ppr log.
Question is, should I move _BOTH_ these checks into softirq or just
defer event log processing, and leave ppr log handling in hard-irq
context? Quickly looking at the new specs, it seems to me that deferring
both should be fine, but I'd really appreciate your thoughts...
Wei, Jan, Tim?
Thanks and regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-------------------------------------------------------------------
Dario Faggioli, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
PhD Candidate, ReTiS Lab, Scuola Superiore Sant'Anna, Pisa (Italy)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2012-01-18 8:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 15:10 [PATCHv2 0 of 2] Deal with IOMMU faults in softirq context Dario Faggioli
2012-01-05 15:25 ` [PATCHv2 1 of 2] Move IOMMU faults handling into softirq for VT-d Dario Faggioli
2012-01-17 11:17 ` Keir Fraser
2012-01-05 15:27 ` [PATCHv2 2 of 2] Move IOMMU faults handling into softirq for AMD-Vi Dario Faggioli
2012-01-17 11:17 ` Keir Fraser
2012-01-18 8:53 ` Dario Faggioli [this message]
2012-01-18 10:40 ` Wei Wang
2012-01-18 10:59 ` Dario Faggioli
2012-01-18 13:51 ` [PATCHv3] " Dario Faggioli
2012-01-18 15:53 ` Wei Wang
2012-01-18 15:57 ` Dario Faggioli
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=1326876800.2375.18.camel@Abyss \
--to=raistlin@linux.it \
--cc=JBeulich@suse.com \
--cc=allen.m.kay@intel.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--cc=wei.wang2@amd.com \
--cc=xen-devel@lists.xensource.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).