From: Thomas Gleixner <tglx@linutronix.de>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"M. Vefa Bicakci" <m.v.b@runbox.com>,
linux-kernel@vger.kernel.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Juergen Gross <jgross@suse.com>,
xen-devel@lists.xenproject.org, x86@kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] xen/pv: Call get_cpu_address_sizes to set x86_virt/phys_bits
Date: Mon, 6 Aug 2018 22:16:33 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1808062216130.1788@nanos.tec.linutronix.de> (raw)
In-Reply-To: <7c07bb2f-e825-66bf-f517-86f893cd9e8b@oracle.com>
On Mon, 6 Aug 2018, Boris Ostrovsky wrote:
> x86 maintainers, this needs your ack please.
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
next prev parent reply other threads:[~2018-08-06 20:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 19:49 [PATCH 1/2] x86/entry/64: Do not clear %rbx under Xen M. Vefa Bicakci
2018-07-21 19:49 ` [PATCH 2/2] xen/pv: Call get_cpu_address_sizes to set x86_virt/phys_bits M. Vefa Bicakci
2018-07-21 21:25 ` Boris Ostrovsky
2018-07-21 23:17 ` M. Vefa Bicakci
2018-07-22 15:57 ` M. Vefa Bicakci
2018-07-23 15:04 ` Boris Ostrovsky
2018-07-24 12:42 ` M. Vefa Bicakci
2018-07-24 12:45 ` [PATCH v2] " M. Vefa Bicakci
2018-07-24 14:08 ` Boris Ostrovsky
2018-07-26 3:56 ` [PATCH v3] " M. Vefa Bicakci
2018-08-06 20:15 ` [PATCH v2] " Boris Ostrovsky
2018-08-06 20:16 ` Thomas Gleixner [this message]
2018-08-06 21:27 ` Boris Ostrovsky
2018-08-07 9:50 ` Ingo Molnar
2018-07-21 21:19 ` [PATCH 1/2] x86/entry/64: Do not clear %rbx under Xen Boris Ostrovsky
2018-07-21 23:18 ` M. Vefa Bicakci
2018-07-23 14:56 ` Boris Ostrovsky
2018-07-21 21:45 ` Andy Lutomirski
2018-07-21 23:19 ` M. Vefa Bicakci
2018-07-21 23:30 ` Andy Lutomirski
2018-07-21 23:37 ` M. Vefa Bicakci
2018-07-22 1:20 ` M. Vefa Bicakci
2018-07-22 17:56 ` Andy Lutomirski
2018-07-22 18:32 ` [Xen-devel] " 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=alpine.DEB.2.21.1808062216130.1788@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=m.v.b@runbox.com \
--cc=mingo@redhat.com \
--cc=stable@vger.kernel.org \
--cc=x86@kernel.org \
--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).