From: Alex Williamson <alex.williamson@redhat.com>
To: "Roedel, Joerg" <Joerg.Roedel@amd.com>
Cc: Florian Dazinger <florian@dazinger.net>,
linux-kernel@vger.kernel.org,
iommu <iommu@lists.linux-foundation.org>
Subject: Re: 3.6-rc7 boot crash + bisection
Date: Wed, 26 Sep 2012 10:13:58 -0600 [thread overview]
Message-ID: <1348676038.28860.190.camel@bling.home> (raw)
In-Reply-To: <20120926150407.GD10549@amd.com>
On Wed, 2012-09-26 at 17:04 +0200, Roedel, Joerg wrote:
> On Wed, Sep 26, 2012 at 08:52:01AM -0600, Alex Williamson wrote:
> > Assuming this works, it may be ok as a 3.7 fix, but if there was
> > actually more than one device behind the alias we'd expose them as
> > separate iommu groups. I don't think that's what we want. Maybe it
> > should at least get a pr_warn. Thanks,
>
> True, we need something more generic as the real fix. When Florian
> reports success I'll try to get this still into 3.6, otherwise to
> -stable.
Yes, 3.6 is what I meant to type. Thanks,
Alex
next prev parent reply other threads:[~2012-09-26 16:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 19:03 Florian Dazinger
2012-09-25 18:32 ` Alex Williamson
2012-09-25 18:42 ` Alex Williamson
2012-09-25 18:54 ` Florian Dazinger
2012-09-25 19:43 ` Alex Williamson
2012-09-25 23:01 ` Florian Dazinger
2012-09-26 3:12 ` Alex Williamson
2012-09-26 14:43 ` Roedel, Joerg
2012-09-26 14:52 ` Alex Williamson
2012-09-26 15:04 ` Roedel, Joerg
2012-09-26 16:13 ` Alex Williamson [this message]
2012-09-26 16:43 ` Florian Dazinger
2012-09-26 17:47 ` Florian Dazinger
2012-09-26 13:20 ` Roedel, Joerg
2012-09-26 14:35 ` Alex Williamson
2012-09-26 15:10 ` Roedel, Joerg
2012-09-26 16:21 ` Alex Williamson
2012-09-26 19:50 ` Alex Williamson
2012-09-26 22:04 ` Alex Williamson
2012-09-27 16:22 ` Florian Dazinger
2012-09-28 13:58 ` Roedel, Joerg
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=1348676038.28860.190.camel@bling.home \
--to=alex.williamson@redhat.com \
--cc=Joerg.Roedel@amd.com \
--cc=florian@dazinger.net \
--cc=iommu@lists.linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®