From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [PATCH] KVM: x86: Run PIT work in own kthread Date: Tue, 17 Apr 2012 13:18:30 +0200 Message-ID: <4F8D5186.7020801@siemens.com> References: <4F8C645C.7010302@siemens.com> <4F8D4598.5080902@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , kvm , Linux Kernel Mailing List To: Avi Kivity Return-path: In-Reply-To: <4F8D4598.5080902@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 2012-04-17 12:27, Avi Kivity wrote: > On 04/16/2012 09:26 PM, Jan Kiszka wrote: >> We can't run PIT IRQ injection work in the interrupt context of the host >> timer. This would allow the user to influence the handler complexity by >> asking for a broadcast to a large number of VCPUs. Therefore, this work >> was pushed into workqueue context in 9d244caf2e. However, this prevents >> prioritizing the PIT injection over other task as workqueues share >> kernel threads. >> >> This replaces the workqueue with a kthread worker and gives that thread >> a name in the format "kvm-pit/". That allows to >> identify and adjust the kthread priority according to the VM process >> parameters. > > Is this a new ABI? Yep. Scripts will use it, maybe even QEMU. Do you want this to appear in api.txt? > > Patch looks reasonable. > Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux