LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com> To: David Vrabel <david.vrabel@citrix.com> Cc: Jan Beulich <JBeulich@suse.com>, "Luis R. Rodriguez" <mcgrof@do-not-panic.com>, Andy Lutomirski <luto@amacapital.net>, Steven Rostedt <rostedt@goodmis.org>, Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>, x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>, Paul McKenney <paulmck@linux.vnet.ibm.com>, xen-devel@lists.xenproject.org, boris.ostrovsky@oracle.com, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@suse.de>, kvm@vger.kernel.org, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "H. Peter Anvin" <hpa@zytor.com> Subject: Re: [PATCH v5 2/2] x86/xen: allow privcmd hypercalls to be preempted on 64-bit Date: Mon, 2 Feb 2015 16:24:57 -0800 [thread overview] Message-ID: <CAB=NE6XTv3hKOr=9gowTBry6Je=LOA+cJGu4wRawU-ur31z+4g@mail.gmail.com> (raw) In-Reply-To: <20150129203531.GF19988@wotan.suse.de> On Thu, Jan 29, 2015 at 12:35 PM, Luis R. Rodriguez <mcgrof@suse.com> wrote: > On Tue, Jan 27, 2015 at 10:06:44AM +0000, David Vrabel wrote: >> On 27/01/15 08:35, Jan Beulich wrote: >> >>>> On 27.01.15 at 02:51, <mcgrof@do-not-panic.com> wrote: >> > >> > Even if David told you this would be acceptable, I have to question >> > an abstract model of fixing issues on only 64-bit kernels - this may >> > be acceptable for distro purposes, but seems hardly the right >> > approach for upstream. If 32-bit ones are to become deliberately >> > broken, the XEN config option should become dependent on !X86_32. >> >> I'd rather have something omitted (keeping the current behaviour) than >> something that has not been tested at all. >> >> Obviously it would be preferable to to fix both 32-bit and 64-bit x86 >> (and ARM as well) but I'm not going to block an important bug fix for >> the majority use case (64-bit x86). > > Hey folks, what is the status of these patches? Any more feedback? As I waited I decided to finally install a 32-bit OS but I found now that as of Xen commit 5d1181a5 which went upstream as of xen 4.3 Xen no longer supports 32-bit for x86. So -- Xen no loner even builds on 32-bit systems. The latest version I could use then would be Xen 4.2 but the even the stable-4.2 branch fails to build for me even after fixing quite a bit of compile failures, I'm just going to give up now. I want to build Xen as I'm relying on some customized emulated delays on the hypervisor in order to test the issue, otherwise I'd have to dedicate a huge system to reproduce this issue. While it is possible folks on old xen may use newer kernels this issue is likely not a high priority on those 32-bit systems and likely hard to reproduce there. When and if someone is able to test this on a 32-bit kernel / hypervisor then they can test the small patch below. Can we move forward with the 64-bit part then? diff --git a/arch/x86/kernel/entry_32.S b/arch/x86/kernel/entry_32.S index 000d419..b4b1f42 100644 --- a/arch/x86/kernel/entry_32.S +++ b/arch/x86/kernel/entry_32.S @@ -982,6 +982,8 @@ ENTRY(xen_hypervisor_callback) ENTRY(xen_do_upcall) 1: mov %esp, %eax call xen_evtchn_do_upcall + movl %esp,%eax + call xen_end_upcall jmp ret_from_intr CFI_ENDPROC ENDPROC(xen_hypervisor_callback)
next prev parent reply other threads:[~2015-02-03 0:25 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-27 1:51 [PATCH v5 0/2] x86/xen: add xen hypercall preemption Luis R. Rodriguez 2015-01-27 1:51 ` [PATCH v5 1/2] xen: add xen_is_preemptible_hypercall() Luis R. Rodriguez 2015-02-03 11:05 ` [Xen-devel] " David Vrabel 2015-02-03 18:03 ` Luis R. Rodriguez 2015-01-27 1:51 ` [PATCH v5 2/2] x86/xen: allow privcmd hypercalls to be preempted on 64-bit Luis R. Rodriguez 2015-01-27 8:35 ` Jan Beulich 2015-01-27 10:01 ` [Xen-devel] " Andrew Cooper 2015-01-27 10:06 ` David Vrabel 2015-01-27 20:12 ` Luis R. Rodriguez 2015-01-29 20:35 ` Luis R. Rodriguez 2015-02-03 0:24 ` Luis R. Rodriguez [this message] 2015-02-03 9:58 ` David Vrabel 2015-02-05 12:47 ` [Xen-devel] [PATCH v5 0/2] x86/xen: add xen hypercall preemption David Vrabel 2015-02-05 18:15 ` Luis R. Rodriguez
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='CAB=NE6XTv3hKOr=9gowTBry6Je=LOA+cJGu4wRawU-ur31z+4g@mail.gmail.com' \ --to=mcgrof@do-not-panic.com \ --cc=JBeulich@suse.com \ --cc=boris.ostrovsky@oracle.com \ --cc=bp@suse.de \ --cc=david.vrabel@citrix.com \ --cc=hpa@zytor.com \ --cc=konrad.wilk@oracle.com \ --cc=kvm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=luto@amacapital.net \ --cc=masami.hiramatsu.pt@hitachi.com \ --cc=mingo@redhat.com \ --cc=paulmck@linux.vnet.ibm.com \ --cc=rostedt@goodmis.org \ --cc=tglx@linutronix.de \ --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: linkBe 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).