All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Paul Durrant <paul.durrant@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 1/2] x86/hvm: make sure HVM_PARAM_[BUF]IOREQ_PFN can only be set once
Date: Mon, 08 Oct 2018 07:16:17 -0600	[thread overview]
Message-ID: <5BBB58A102000078001EF969@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <20181005134334.2645-2-paul.durrant@citrix.com>

>>> On 05.10.18 at 15:43, <paul.durrant@citrix.com> wrote:
> These parameters should have always been in the 'set once' category
> but this has, so far, not been enforced.

But now that we're not even handling these anymore, why is there a
need to start doing so? If anything wouldn't it be better to add them
to the deprecated group in that same function (and maybe also its
"get" counterpart)?

Jan



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

  reply	other threads:[~2018-10-08 13:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05 13:43 [PATCH 0/2] ioreq: make use of 'legacy' GFNs Paul Durrant
2018-10-05 13:43 ` [PATCH 1/2] x86/hvm: make sure HVM_PARAM_[BUF]IOREQ_PFN can only be set once Paul Durrant
2018-10-08 13:16   ` Jan Beulich [this message]
2018-10-08 13:20   ` Jan Beulich
2018-10-08 13:21     ` Paul Durrant
2018-10-05 13:43 ` [PATCH 2/2] x86/hvm/ioreq: allow ioreq servers to use HVM_PARAM_[BUF]IOREQ_PFN Paul Durrant
2018-10-08 13:29   ` Jan Beulich
2018-10-08 14:38     ` Paul Durrant
2018-10-08 14:59       ` Jan Beulich
2018-10-08 15:05         ` 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=5BBB58A102000078001EF969@prv1-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=paul.durrant@citrix.com \
    --cc=wei.liu2@citrix.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.