All of lore.kernel.org
 help / color / mirror / Atom feed
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 09:35:40 -0500	[thread overview]
Message-ID: <20091222143540.GB2785@phenom.dumpdata.com> (raw)
In-Reply-To: <1261473615.5965.3829.camel@zakaz.uk.xensource.com>

On Tue, Dec 22, 2009 at 09:20:15AM +0000, Ian Campbell wrote:
> On Tue, 2009-12-22 at 08:42 +0000, Pasi Kärkkäinen wrote:
> > >    (early) [    0.000000] PCI-DMA: Using Xen software bounce
> > buffering for IO
> > >    (Xen-SWIOTLB)
> > >    (early) [    0.000000] Kernel panic - not syncing:
> > >    <3>xen_create_contiguous_region failed
> > > 
> > 
> > Did you try cgroup_disable=memory kernel option? 
> 
> I think this is more likely to relate to the failure to initialise
> swiotlb due to the failure of xen_create_contiguous_region, leading to a
> panic. IIRC the guest won't be privileged enough to make this call
> unless it has PCI passthrough enabled.

Not so. You can still make the call even if you don't have PCI passthrough
enabled. The up call is just to replace MFNs.

> 
> In a pre-pvops kernel the swiotlb would be inactive in a domU unless
> specifically requested on the command line but in Jeremy's xen/master
> branch it looks like it is unconditionally enabled for dom0 and domU as
> a consequence of:
>         commit 4bc6b1a9dd5d7447af8c3d27c1449f73f5f764ec
>         Author: root <root@localhost.localdomain>
>         Date:   Thu Nov 5 16:33:10 2009 -0500
>         
>             Enable Xen-SWIOTLB if running in [non-]privileged and disable the Xen-IOMMU if an IOMMU is detected.
> 
> On a related note I don't think the xen-swiotlb code should panic() if
> it cannot allocate the contiguous region (at least in domU). Chances are

I concur. It should also give the error code. I am working on re-writting that
code since the upstream now has some form of registration/de-registration that
we could take advantage off.

> if it hasn't got privilege to make the fixups it isn't going to have any
> devices.
> 
> Ian.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  parent reply	other threads:[~2009-12-22 14:35 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 [this message]
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
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=20091222143540.GB2785@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.