From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH Master]
Date: Tue, 22 Dec 2009 15:20:54 -0500 [thread overview]
Message-ID: <20091222202054.GA11542@phenom.dumpdata.com> (raw)
In-Reply-To: <4B312972.9020800@goop.org>
On Tue, Dec 22, 2009 at 12:17:54PM -0800, Jeremy Fitzhardinge wrote:
> On 12/22/2009 11:04 AM, Konrad Rzeszutek Wilk wrote:
>> Originally I was thinking it should go to to origin/xen/dom0/swiotlb-new,
>> but that has a different logic that in which this patch would not
>> work properly (the drivers/pci/xen-iommu.c initializes itself irregardless
>> if the Xen-SWIOTLB had been initialized before).
>
> Are you saying that the logic of xen/master is different from its
> constituent branches?
Yes for the SWIOTLB. You added the 'xen_swiotlb' flag which is not yet
in the xen/master tree.
>
>> I would have
>> posted a couple of patches for that branch (swiotlb-new) but alas,
>> I am going to be on vacation for the next couple of days.
>>
>
> No problem. I'm taking a long break over Christmas/NY (visit family in
> Australia) and will be back on Jan 18th. I expect I'll be tracking
> email, but I won't be doing anything major.
Enjoy your holidays!
(the posting to the other branches are not that important - they can
wait after New Year).
prev parent reply other threads:[~2009-12-22 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 19:04 [PATCH Master] Konrad Rzeszutek Wilk
2009-12-22 19:05 ` [PATCH] [xen/swiotlb] Enable Xen-SWIOTLB only if running in privileged domain or if in non-privileged with iommu=soft Konrad Rzeszutek Wilk
2009-12-22 20:17 ` [PATCH Master] Jeremy Fitzhardinge
2009-12-22 20:20 ` Konrad Rzeszutek Wilk [this message]
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=20091222202054.GA11542@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jeremy@goop.org \
--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.