virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org, mingo@redhat.com,
	david.vrabel@citrix.com, luto@kernel.org, hpa@zytor.com,
	xen-devel@lists.xenproject.org, tglx@linutronix.de, bp@suse.de
Subject: Re: [PATCH 2/3] x86: irq_enable_sysexit pv op is no longer needed
Date: Wed, 18 Nov 2015 15:34:32 -0500	[thread overview]
Message-ID: <564CE0D8.1030004@oracle.com> (raw)
In-Reply-To: <20151118201152.GA6094@char.us.oracle.com>

On 11/18/2015 03:11 PM, Konrad Rzeszutek Wilk wrote:
> On Wed, Nov 18, 2015 at 03:06:18PM -0500, Boris Ostrovsky wrote:
>> Xen PV guests have been the only ones using it and now they don't.
> Could you elaborate on the 'now they don't' please?
>
> Is Xen not doing it? Did it do it in the past?
>
> Is it because the Linux code paths will never run to this in Xen PV mode?
> Is that due to other patches? If so please mention the name
> of the other patches.. (so if somebody is thinking to put the
> other patches on the stable train they should also take these ones).

Since this is due to the first patch in the series I don't know its 
commitID. Should I just refer to patch title?

-boris

  parent reply	other threads:[~2015-11-18 20:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1447877179-2775-1-git-send-email-boris.ostrovsky@oracle.com>
2015-11-18 20:06 ` [PATCH 1/3] x86/xen: Avoid fast syscall path for Xen PV guests Boris Ostrovsky
2015-11-18 20:06 ` [PATCH 2/3] x86: irq_enable_sysexit pv op is no longer needed Boris Ostrovsky
2015-11-18 20:06 ` [PATCH 3/3] x86: usergs_sysret32 " Boris Ostrovsky
     [not found] ` <1447877179-2775-2-git-send-email-boris.ostrovsky@oracle.com>
2015-11-18 20:21   ` [PATCH 1/3] x86/xen: Avoid fast syscall path for Xen PV guests Andy Lutomirski
2015-11-18 20:47     ` Borislav Petkov
2015-11-18 20:50     ` Brian Gerst
     [not found]     ` <CAMzpN2iofkEeYkiZa8FRJ5gbz5smPbV0COOye9wZ9OhV6pBfow@mail.gmail.com>
2015-11-18 20:58       ` Andy Lutomirski
2015-11-18 22:05         ` Boris Ostrovsky
2015-11-19 12:08     ` Borislav Petkov
     [not found] ` <1447877179-2775-3-git-send-email-boris.ostrovsky@oracle.com>
2015-11-18 20:23   ` [PATCH 2/3] x86: irq_enable_sysexit pv op is no longer needed Andy Lutomirski
     [not found]   ` <20151118201152.GA6094@char.us.oracle.com>
2015-11-18 20:34     ` Boris Ostrovsky [this message]
     [not found] ` <1447877179-2775-4-git-send-email-boris.ostrovsky@oracle.com>
2015-11-18 20:26   ` [PATCH 3/3] x86: usergs_sysret32 " Andy Lutomirski
2015-11-19 12:10 ` [PATCH 0/3] Fix and cleanup for 32-bit PV sysexit Borislav Petkov

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=564CE0D8.1030004@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=bp@suse.de \
    --cc=david.vrabel@citrix.com \
    --cc=hpa@zytor.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=virtualization@lists.linux-foundation.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).