From: "Jürgen Groß" <jgross@suse.com>
To: Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Paul Durrant <paul@xen.org>
Subject: Re: [Xen-devel] [PATCH v7 1/3] AMD/IOMMU: allocate one device table per PCI segment
Date: Mon, 7 Oct 2019 12:19:32 +0200 [thread overview]
Message-ID: <f0c08d79-fad2-4760-6e18-99bfe84509e2@suse.com> (raw)
In-Reply-To: <ee24c8e1-c925-f78e-1d51-d0d1f03f7326@suse.com>
On 07.10.19 12:03, Jan Beulich wrote:
> I appreciate the ack, but I think I'd prefer to not make use of it
> if at all possible under these conditions. Instead I'd like us to
> reach some common ground here. Seeing that we're past the deadline
> already, Jürgen's release ack will now be needed anyway. Jürgen -
> would you be fine with settling on this taking a few more days,
> and then still allow in this series? Or is trying to soon find a
> resolution here pointless as you'd rather not see this go in
> anymore?
As it isn't a completely trivial patch series I'd like to know what
the gain would be: is it just a "nice to have", does it solve a
theoretical (not to be expected) problem, or do you think it will
be needed to be backported if I say "no"?
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-10-07 10:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 14:26 [Xen-devel] [PATCH v7 0/3] AMD IOMMU: further improvements Jan Beulich
2019-09-26 14:28 ` [Xen-devel] [PATCH v7 1/3] AMD/IOMMU: allocate one device table per PCI segment Jan Beulich
2019-10-04 13:18 ` Andrew Cooper
2019-10-04 13:30 ` Jan Beulich
2019-10-04 17:28 ` Andrew Cooper
2019-10-07 10:03 ` Jan Beulich
2019-10-07 10:19 ` Jürgen Groß [this message]
2019-10-07 10:49 ` Jan Beulich
2019-10-07 11:25 ` Jürgen Groß
2019-10-10 5:57 ` Jan Beulich
2019-10-10 6:12 ` Jürgen Groß
2019-09-26 14:29 ` [Xen-devel] [PATCH v7 2/3] AMD/IOMMU: allow callers to request allocate_buffer() to skip its memset() Jan Beulich
2019-10-04 13:26 ` Andrew Cooper
2019-10-04 13:33 ` Jan Beulich
2019-09-26 14:29 ` [Xen-devel] [PATCH v7 3/3] AMD/IOMMU: pre-fill all DTEs right after table allocation Jan Beulich
2019-10-04 13:43 ` Andrew Cooper
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=f0c08d79-fad2-4760-6e18-99bfe84509e2@suse.com \
--to=jgross@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=paul@xen.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=xen-devel@lists.xenproject.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).