linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhenzhong Duan <zhenzhong.duan@oracle.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	linux-kernel@vger.kernel.org
Cc: xen-devel@lists.xenproject.org, jgross@suse.com,
	sstabellini@kernel.org, tglx@linutronix.de, mingo@redhat.com,
	bp@alien8.de
Subject: Re: [PATCH v4 5/5] xen: Add 'xen_nopv' parameter back for backward compatibility
Date: Wed, 3 Jul 2019 10:14:20 +0800	[thread overview]
Message-ID: <cd07bf77-11e6-5aca-9449-ffad8aea95cb@oracle.com> (raw)
In-Reply-To: <603e1c8a-408b-360d-9a84-6d91b5f1db1b@oracle.com>


On 2019/7/3 2:13, Boris Ostrovsky wrote:
> On 7/1/19 1:19 AM, Zhenzhong Duan wrote:
>> Map 'xen_nopv' to 'nopv' and mark 'xen_nopv' obsolete in
>> kernel-parameters.txt
> I am not sure we want patch #3, why not do everything in a single patch?
>
Thanks for review. I'll fix all those based on your comments.

Zhenzhong


      reply	other threads:[~2019-07-03  2:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01  5:19 [PATCH v4 0/5] misc fixes to PV extentions code Zhenzhong Duan
2019-07-01  5:19 ` [PATCH v4 1/5] x86/xen: Mark xen_hvm_need_lapic() and xen_x2apic_para_available() as __init Zhenzhong Duan
2019-07-01  5:19 ` [PATCH v4 2/5] x86: Add nopv parameter to disable PV extensions Zhenzhong Duan
2019-07-02 17:47   ` Boris Ostrovsky
2019-07-01  5:19 ` [PATCH v4 3/5] Revert "xen: Introduce 'xen_nopv' to disable PV extensions for HVM guests." Zhenzhong Duan
2019-07-01  5:19 ` [PATCH v4 4/5] x86/xen: Add 'nopv' support for HVM guest Zhenzhong Duan
2019-07-02 18:04   ` Boris Ostrovsky
2019-07-01  5:19 ` [PATCH v4 5/5] xen: Add 'xen_nopv' parameter back for backward compatibility Zhenzhong Duan
2019-07-02 18:13   ` Boris Ostrovsky
2019-07-03  2:14     ` Zhenzhong Duan [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=cd07bf77-11e6-5aca-9449-ffad8aea95cb@oracle.com \
    --to=zhenzhong.duan@oracle.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=bp@alien8.de \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=sstabellini@kernel.org \
    --cc=tglx@linutronix.de \
    --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).