From: Keith Packard <keithp@keithp.com>
To: Josh Boyer <jwboyer@redhat.com>
Cc: Dave Jones <davej@redhat.com>, Yang Bai <hamo.by@gmail.com>,
Fengguang Wu <fengguang.wu@intel.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Fedora Kernel Team <kernel-team@fedoraproject.org>,
kernel@tesarici.cz, David Woodhouse <dwmw2@infradead.org>
Subject: Re: inode->i_wb_list corruption.
Date: Fri, 09 Mar 2012 14:44:49 -0800 [thread overview]
Message-ID: <861up175su.fsf@sumi.keithp.com> (raw)
In-Reply-To: <20120309201934.GN17489@zod.bos.redhat.com>
<#part sign=pgpmime>
On Fri, 9 Mar 2012 15:19:34 -0500, Josh Boyer <jwboyer@redhat.com> wrote:
> Is the VT-d issue something in the hardware itself, or do you mean if
> you have it enabled in the kernel? We've had the intel IOMMU disabled
> by default in the Fedora kernels for a while now. At least since before
> 3.2 was released.
I don't know for sure; David Woodhouse gave a scary presentation
yesterday that makes me unsure of what happens when IOMMU is disabled in
the kernel, given that much of the hardware is setup by the BIOS.
--
keith.packard@intel.com
next prev parent reply other threads:[~2012-03-09 22:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 18:51 inode->i_wb_list corruption Dave Jones
2012-03-06 21:03 ` Jan Kara
2012-03-07 7:26 ` Fengguang Wu
2012-03-07 10:42 ` Jan Kara
2012-03-09 8:34 ` Yang Bai
2012-03-09 14:57 ` Dave Jones
2012-03-09 15:19 ` Dave Jones
2012-03-09 16:14 ` Yang Bai
2012-03-09 18:00 ` Dave Jones
2012-03-09 20:08 ` Keith Packard
2012-03-09 20:19 ` Josh Boyer
2012-03-09 22:44 ` Keith Packard [this message]
2012-03-12 21:13 ` Josh Boyer
2012-03-12 21:27 ` David Woodhouse
2012-03-12 23:26 ` Dave Jones
2012-03-13 0:06 ` Keith Packard
-- strict thread matches above, loose matches on Subject: below --
2012-03-15 14:08 Petr Tesařík
2012-03-15 14:22 ` Dave Airlie
2012-03-15 14:49 ` Dave Jones
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=861up175su.fsf@sumi.keithp.com \
--to=keithp@keithp.com \
--cc=davej@redhat.com \
--cc=dwmw2@infradead.org \
--cc=fengguang.wu@intel.com \
--cc=hamo.by@gmail.com \
--cc=jwboyer@redhat.com \
--cc=kernel-team@fedoraproject.org \
--cc=kernel@tesarici.cz \
--cc=linux-kernel@vger.kernel.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 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.