All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Paul Durrant <paul.durrant@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Brian Woods <brian.woods@amd.com>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: [PATCH v2] amd-iommu: remove page merging code
Date: Tue, 27 Nov 2018 09:38:24 -0700	[thread overview]
Message-ID: <5BFD7300020000780020077D@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <0c1c8dba2ab14ea998cd4fb0c16cb458@AMSPEX02CL03.citrite.net>

>>> On 27.11.18 at 17:05, <Paul.Durrant@citrix.com> wrote:
> Well, I could just leave PV-IOMMU unimplemented for AMD h/w if you think the 
> page merging code is more important since, without the spare ignored bits, I 
> have no way to track pages added by the hypercall vs. those added at start of 
> day. I personally think that the simpler code is worthwhile in itself but I 
> guess you disagree.

Not exactly: With a proper reason (here: you need to free up at least
one of the bits; "for other potential use" simply is too vague for my
taste, and to be honest I had already forgotten about this need of
yours), I can live with this. Plus I'm not the maintainer of this code
anyway.

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-11-27 16:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 14:58 [PATCH v2] amd-iommu: remove page merging code Paul Durrant
2018-11-27 15:57 ` Jan Beulich
2018-11-27 16:05   ` Paul Durrant
2018-11-27 16:38     ` Jan Beulich [this message]
2018-11-27 16:40       ` Paul Durrant

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=5BFD7300020000780020077D@prv1-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=brian.woods@amd.com \
    --cc=paul.durrant@citrix.com \
    --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 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.