From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
?????? <peb1611@gmail.com>
Subject: Re: I cannot get any message from domU by console / pv_ops domU kernel crashes with xen_create_contiguous_region failed
Date: Tue, 22 Dec 2009 11:59:05 -0500 [thread overview]
Message-ID: <20091222165905.GA13650@phenom.dumpdata.com> (raw)
In-Reply-To: <20091222161919.GA6426@phenom.dumpdata.com>
On Tue, Dec 22, 2009 at 11:19:19AM -0500, Konrad Rzeszutek Wilk wrote:
> On Tue, Dec 22, 2009 at 04:09:36PM +0000, Ian Campbell wrote:
> > On Tue, 2009-12-22 at 15:47 +0000, Konrad Rzeszutek Wilk wrote:
> > > > I thought it used to be that you could only (successfully) make order>0
> > > > increase_reservation or mem_exchange hypercalls if you had I/O
> > > > privileges? Has this changed?
> > >
> > > I am looking at the 3.4 code I am not seeing any I/O privileges check.
> > >
> > > I did not even know that those existed actually - could you give me an idea
> > > when was the last time you saw it?
> >
> > In xen-unstable multipage_allocation_permitted is called from
> > memory_exchange() and increase_reservation() and is defined as
> > #define multipage_allocation_permitted(d, order) \
> > (((order) <= 9) || /* allow 2MB superpages */ \
> > !rangeset_is_empty((d)->iomem_caps) || \
> > !rangeset_is_empty((d)->arch.ioport_caps))
> >
> > The ((order) <= 9) || is new and isn't present in the 3.4 tree,
> > previously you would have had to add a passthrough device to cause one
> > of the other rangesets to become non-empty.
>
> AAh, and since the exchange of memory is done in small chunks we pass
> underneath the radar even if did not have the passthrough device set.
>
> Ian, thanks for finding the culprit. Let me roll out a patch that
> will do what was done in the past (ie, turn SWIOTLB for DomU only
> when iommu=soft was passed in) as a fix.
Jeremy,
Please consider this patch to the PV-OPS tree.
[xen/swiotlb] Enable Xen-SWIOTLB only if running in privileged domain or if in non-privileged with iommu=soft.
Previous to this patch we would unconditionally enable Xen-SWIOTLB
if running in PV context. That does not work with Xen 3.4.2 as it has a
security check to disable exchanging of MFNs if no PCI devices have been
passed through. In 4.0 there is an additional check to allow 2MB super-pages
- we accidentally circumvented that by exchanging pages under the 2MB chunk size
even without any PCI devices passed through.
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
diff --git a/arch/x86/xen/pci-swiotlb.c b/arch/x86/xen/pci-swiotlb.c
index ecdbfe2..7fdfccc 100644
--- a/arch/x86/xen/pci-swiotlb.c
+++ b/arch/x86/xen/pci-swiotlb.c
@@ -960,7 +960,7 @@ xen_swiotlb_fixup(void *buf, size_t size, unsigned long nslabs)
dma_bits);
} while (rc && dma_bits++ < max_dma_bits);
if (rc)
- panic(KERN_ERR "xen_create_contiguous_region failed\n");
+ panic(KERN_ERR "xen_create_contiguous_region failed: rc: %d\n", rc);
i += slabs;
} while(i < nslabs);
@@ -984,7 +984,16 @@ static struct dma_map_ops xen_swiotlb_dma_ops = {
void __init xen_swiotlb_init(void)
{
- if (xen_domain()) {
+ int use_swiotlb = 0;
+
+ if (xen_initial_domain())
+ use_swiotlb = 1;
+
+ /* For PV guest, only if iommu=soft is passed in. */
+ if (xen_pv_domain() && !xen_initial_domain() && swiotlb)
+ use_swiotlb = 1;
+
+ if (use_swiotlb) {
printk(KERN_INFO "PCI-DMA: Using Xen software bounce buffering for IO (Xen-SWIOTLB)\n");
xen_swiotlb_init_with_default_size(64 * (1<<20)); /* default to 64MB */
dma_ops = &xen_swiotlb_dma_ops;
next prev parent reply other threads:[~2009-12-22 16:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 14:30 I cannot get any message from domU by console 박은병
2009-12-21 18:30 ` Pasi Kärkkäinen
[not found] ` <ebf0d9030912212002h6996f725kf4626bd02e03161b@mail.gmail.com>
2009-12-22 8:42 ` I cannot get any message from domU by console / pv_ops domU kernel crashes with xen_create_contiguous_region failed Pasi Kärkkäinen
2009-12-22 9:20 ` Ian Campbell
2009-12-22 13:04 ` Michael D Labriola
2009-12-22 13:20 ` Michael D Labriola
2009-12-22 14:09 ` Ian Campbell
2009-12-22 13:33 ` 박은병
2009-12-22 14:35 ` Konrad Rzeszutek Wilk
2009-12-22 14:50 ` Ian Campbell
2009-12-22 15:47 ` Konrad Rzeszutek Wilk
2009-12-22 16:09 ` Ian Campbell
2009-12-22 16:19 ` Konrad Rzeszutek Wilk
2009-12-22 16:59 ` Konrad Rzeszutek Wilk [this message]
2009-12-22 18:02 ` Ian Campbell
2009-12-22 18:08 ` Konrad Rzeszutek Wilk
2009-12-22 14:32 ` Konrad Rzeszutek Wilk
2009-12-22 14:58 ` Ian Campbell
2009-12-22 15:27 ` Konrad Rzeszutek Wilk
2009-12-22 15:14 ` Michael D Labriola
2009-12-22 15:40 ` Konrad Rzeszutek Wilk
2009-12-22 16:44 ` Michael D Labriola
2009-12-22 16:55 ` Michael D Labriola
2009-12-22 17:00 ` Konrad Rzeszutek Wilk
2009-12-22 17:20 ` Michael D Labriola
2009-12-22 17:59 ` Michael D Labriola
2009-12-22 18:23 ` Konrad Rzeszutek Wilk
2009-12-22 18:47 ` Michael D Labriola
2009-12-22 19:14 ` Konrad Rzeszutek Wilk
2009-12-22 19:50 ` Michael D Labriola
2009-12-22 20:03 ` Ian Campbell
2009-12-22 21:00 ` Michael D Labriola
2009-12-22 20:07 ` Konrad Rzeszutek Wilk
2009-12-22 20:37 ` Konrad Rzeszutek Wilk
2009-12-22 21:49 ` Michael D Labriola
2009-12-23 18:49 ` Michael D Labriola
2009-12-23 20:15 ` Michael D Labriola
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=20091222165905.GA13650@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=jeremy@goop.org \
--cc=peb1611@gmail.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 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.