From: David Woodhouse <dwmw2@infradead.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
Vinod Koul <vinod.koul@intel.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Jesse Barnes <jbarnes@virtuousgeek.org>,
iommu@lists.linux-foundation.org,
Dan Williams <dan.j.williams@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] pci, dmar: Update dmar units devices list during hotplug
Date: Tue, 24 May 2011 11:58:15 +0100 [thread overview]
Message-ID: <1306234696.7218.14.camel@i7.infradead.org> (raw)
In-Reply-To: <1305843308.3100.10.camel@x201>
On Thu, 2011-05-19 at 16:15 -0600, Alex Williamson wrote:
> I think I'd vote for saving some kind of representation of the bus
> hierarchy, we probably don't need to list every possible individual
> device. Leaving a broken pointer around to be matched up and restored
> later just seems like a continuation of an idea that was bad to begin
> with. Thanks,
I agree. We should just process the original ATSR information in
dmar_find_matched_drhd_unit(), rather than comparing with a list of
possibly stale pointers.
I don't quite understand why the list of PCI devices was *ever* done
like that.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2011-05-24 10:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 18:48 Yinghai Lu
2011-05-19 22:15 ` Alex Williamson
2011-05-24 10:58 ` David Woodhouse [this message]
2011-05-24 17:42 ` Alex Williamson
2011-05-24 18:11 ` Yinghai Lu
2011-05-24 19:34 ` Yinghai Lu
2011-05-24 20:07 ` Alex Williamson
2011-05-24 20:24 ` Yinghai Lu
2011-05-24 20:34 ` Alex Williamson
2011-05-24 21:45 ` Yinghai Lu
2011-05-24 22:38 ` Alex Williamson
2011-05-24 23:02 ` Yinghai Lu
2011-05-25 5:42 ` Yinghai Lu
2011-05-25 5:45 ` Yinghai Lu
2011-05-25 12:43 ` Alex Williamson
2011-05-28 22:11 ` David Woodhouse
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=1306234696.7218.14.camel@i7.infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=vinod.koul@intel.com \
--cc=yinghai@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®