All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
	mingo@redhat.com, peterz@infradead.org, tglx@linutronix.de,
	konrad.wilk@oracle.com, david.vrabel@citrix.com,
	masami.hiramatsu.pt@hitachi.com, rostedt@goodmis.org,
	luto@amacapital.net, JBeulich@suse.com, jgross@suse.com,
	bpoirier@suse.de, x86@kernel.org, xen-devel@lists.xenproject.org,
	linux-kernel@vger.kernel.org, Borislav Petkov <bp@suse.de>
Subject: Re: [PATCH v2 2/2] x86/xen: allow privcmd hypercalls to be preempted
Date: Thu, 11 Dec 2014 10:47:44 -0800	[thread overview]
Message-ID: <5489E6D0.8020002@zytor.com> (raw)
In-Reply-To: <20141211010344.GO25677@wotan.suse.de>

On 12/10/2014 05:03 PM, Luis R. Rodriguez wrote:
> 
> This is an issue onloy for for non*-preemptive kernels.
> 
> Some of Xen's hypercalls can take a long time and unfortunately for
> *non*-preemptive kernels this can be quite a bit of an issue.
> We've handled situations like this with cond_resched() before which will
> push even *non*-preemptive kernels to behave as voluntarily preemptive,
> I was not aware to what extent this was done and precedents set but
> its pretety widespread now... this then just addresses once particular
> case where this is also an issuefor but now in IRQ context.
> 
> I agree its a hack but so are all the other cond_reshed() calls then.
> I don't think its a good idea to be spreading use of something like
> this everywhere but after careful review and trying toa void this
> exact code for a while I have not been able to find any other reasonable
> alternative.
> 

This sounds like a patch that is completely unrelated to the rest of the
patch.

	-hpa



  parent reply	other threads:[~2014-12-11 18:48 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10 23:34 [PATCH v2 0/2] x86: add xen hypercall preemption Luis R. Rodriguez
2014-12-10 23:34 ` [PATCH v2 1/2] sched: add cond_resched_irq() Luis R. Rodriguez
2014-12-10 23:34 ` Luis R. Rodriguez
2014-12-11 13:31   ` Jan Beulich
2014-12-11 13:31   ` Jan Beulich
     [not found]   ` <5489AADA020000780004EFB9@suse.com>
2014-12-11 21:06     ` Luis R. Rodriguez
2014-12-11 21:06     ` Luis R. Rodriguez
2014-12-10 23:34 ` [PATCH v2 2/2] x86/xen: allow privcmd hypercalls to be preempted Luis R. Rodriguez
2014-12-10 23:51   ` Andy Lutomirski
2014-12-10 23:51   ` Andy Lutomirski
2014-12-11  0:55     ` Luis R. Rodriguez
2014-12-11  0:55     ` Luis R. Rodriguez
2014-12-11  1:04       ` Andy Lutomirski
2014-12-11  1:04       ` Andy Lutomirski
2014-12-11 11:09     ` [Xen-devel] " David Vrabel
2014-12-11 21:05       ` Luis R. Rodriguez
2014-12-11 21:05       ` [Xen-devel] " Luis R. Rodriguez
2014-12-11 11:09     ` David Vrabel
2014-12-11  0:29   ` H. Peter Anvin
2014-12-11  0:29   ` H. Peter Anvin
2014-12-11  1:03     ` Luis R. Rodriguez
2014-12-11  1:03     ` Luis R. Rodriguez
2014-12-11 18:47       ` H. Peter Anvin
2014-12-11 18:47       ` H. Peter Anvin [this message]
2014-12-11 20:39         ` Luis R. Rodriguez
2014-12-11 20:39         ` Luis R. Rodriguez
2014-12-18 19:23   ` Konrad Rzeszutek Wilk
2014-12-18 19:23   ` [Xen-devel] " Konrad Rzeszutek Wilk
2015-01-13 21:21     ` Luis R. Rodriguez
2015-01-13 21:21     ` [Xen-devel] " Luis R. Rodriguez
2014-12-10 23:34 ` 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=5489E6D0.8020002@zytor.com \
    --to=hpa@zytor.com \
    --cc=JBeulich@suse.com \
    --cc=bp@suse.de \
    --cc=bpoirier@suse.de \
    --cc=david.vrabel@citrix.com \
    --cc=jgross@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mcgrof@do-not-panic.com \
    --cc=mcgrof@suse.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --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: 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.