xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Javier Marcet <jmarcet@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Xen Devel Mailing list <xen-devel@lists.xen.org>
Subject: Re: Xen 4.2.0-rc4 bugs with GigaByte H77M-D3H + Core i7 3770
Date: Sun, 2 Sep 2012 18:30:18 +0200	[thread overview]
Message-ID: <CAAnFQG_vvHQL=NbY1SnMWCcTr73_8RYtNLfc00fqEsz57cd7Rg@mail.gmail.com> (raw)
In-Reply-To: <5040B7A40200007800097CEE@nat28.tlf.novell.com>

On Fri, Aug 31, 2012 at 1:09 PM, Jan Beulich <JBeulich@suse.com> wrote:

> > [    0.358278] DMAR:[DMA Read] Request device [00:02.0] fault addr
> > 9fac7000
> > [    0.358278] DMAR:[fault reason 06] PTE Read access is not set
> > [    0.358286] DRHD: handling fault status reg 2
> > [    0.358288] DMAR:[DMA Read] Request device [00:02.0] fault addr
> > 9fac7000
> > [    0.358288] DMAR:[fault reason 06] PTE Read access is not set
> > [    0.358291] DMAR:[DMA Read] Request device [00:02.0] fault addr
> > 9fac7000
> > [    0.358291] DMAR:[fault reason 06] PTE Read access is not set
> > [    0.358307] DRHD: handling fault status reg 3
> >
> > Furthermore, later on, just after enabling the IOMMU, I get this:
> >
> > [    0.328564] DMAR: No ATSR found
> > [    0.328580] IOMMU 1 0xfed91000: using Queued invalidation
> > [    0.328582] IOMMU: Setting RMRR:
> > [    0.328589] IOMMU: Setting identity map for device 0000:00:1d.0
> > [0x9de36000 - 0x9de52fff]
> > [    0.328606] IOMMU: Setting identity map for device 0000:00:1a.0
> > [0x9de36000 - 0x9de52fff]
> > [    0.328617] IOMMU: Setting identity map for device 0000:00:14.0
> > [0x9de36000 - 0x9de52fff]
> > [    0.328625] IOMMU: Prepare 0-16MiB unity mapping for LPC
> > [    0.328630] IOMMU: Setting identity map for device 0000:00:1f.0
> > [0x0 - 0xffffff]
>
> All of these messages shouldn't appear when running under Xen,
> as it's the hypervisor, not the kernel to take care of the IOMMU(s).
> The logs you had pointers to confirm this - are you sure the above
> was seen when running under Xen?

I'm sorry I didn't make myself clearer. That dmesg output is when booting
WITHOUT xen, that is, linux directly over the bare hardware. Under xen
those errors dissapear.

The big issue I'm having running xen is that I can't use it since xen can't
get the cpu capabilities. On the same kernel, which also has kvm compiled in,
it works fine (kvm).

All the backend xen devices are built-in in the kernel. Frontend devices are
compiled as modules.


--
Javier Marcet <jmarcet@gmail.com>

  reply	other threads:[~2012-09-02 16:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-30 10:43 Xen 4.2.0-rc4 bugs with GigaByte H77M-D3H + Core i7 3770 Javier Marcet
2012-08-30 16:33 ` Konrad Rzeszutek Wilk
2012-08-31 11:09 ` Jan Beulich
2012-09-02 16:30   ` Javier Marcet [this message]
2012-09-02 16:35     ` Javier Marcet
2012-09-03  7:30     ` Jan Beulich
2012-09-03 11:48       ` Javier Marcet
2012-09-04  7:59       ` Javier Marcet
2012-09-04  8:09         ` Jan Beulich
2012-09-04  8:21           ` Javier Marcet
2012-09-02 17:05 ` Javier Marcet

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='CAAnFQG_vvHQL=NbY1SnMWCcTr73_8RYtNLfc00fqEsz57cd7Rg@mail.gmail.com' \
    --to=jmarcet@gmail.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xen.org \
    /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).