All of lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Liu Ping Fan <pingfank@linux.vnet.ibm.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Gleb Natapov <gleb@redhat.com>, "avi@redhat.com" <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH qemu-kvm] Fix: SCI isn't sent on cpu hotplug
Date: Mon, 09 Jan 2012 12:07:48 +0100	[thread overview]
Message-ID: <4F0ACA84.5050309@redhat.com> (raw)
In-Reply-To: <4F0ABF18.8060109@siemens.com>

On 01/09/2012 11:19 AM, Jan Kiszka wrote:
> On 2012-01-09 11:07, Gleb Natapov wrote:
>> On Mon, Jan 09, 2012 at 11:03:10AM +0100, Jan Kiszka wrote:
>>> On 2012-01-09 09:47, Gleb Natapov wrote:
>>>> On Sun, Jan 08, 2012 at 10:40:04PM +0100, Igor Mammedov wrote:
>>>>>   Change introduced by e71f08bb4a
>>>>>      "Fix cpu/pci hotplug to generate level triggered interrupt."
>>>>>   was lost somewhre along the way. And as result SCI is not sent in
>>>>>   case of cpu hotplug event.
>>>>>   Restoring hunk 1 of e71f08bb4a fixes issue.
>>>>>
>>>> Hmm, I sent similar patch [1] last time someone complained about cpu hotplug
>>>> here. Which remind me that in that thread more problem were found in cpu
>>>> hotplug. IIRC Jan collected all the patches. Jan, what happened to
>>>> them?
>>>
>>> My patches should have been superseded by the work of Ping Fan on the
>>> ICC bus.
>>>
>> Didn't they fix some problems with bringing new cpu online, not just
>> making cpu hotplugable in qdev? May be I misremember.
>
> Let me check... Hmm, yes, there were also some bits required to bring up
> the new VCPU thread properly and sync its initial state to the kernel.

CPU bring-up seems to be broken now, guest sees a new cpu but I can't
online it inside guest with error: "CPUx: Not responding". But it
works with old qemu-kvm [3925c857a574].
Jan could you point me to this patches?

> That was not part of Ping Fan's ICC patches, also not of the VCPU life
> cycle patches.

I'm trying to re-base cpu-hotplug to qemu.git, and with ICC patches it's
working like the current qemu-kvm head. But without above mentioned fixes
it seams to be useless.

>
>> BTW do you know
>> what happened with ICC bus patches?
>
> Were forgotten to merge? And/or they lacked some acked-by or
> reviewed-by. :-/
>
> Jan
>

-- 
Thanks,
  Igor

  reply	other threads:[~2012-01-09 11:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-08 21:40 [Qemu-devel] [PATCH qemu-kvm] Fix: SCI isn't sent on cpu hotplug Igor Mammedov
2012-01-09  8:47 ` Gleb Natapov
2012-01-09 10:03   ` Jan Kiszka
2012-01-09 10:07     ` Gleb Natapov
2012-01-09 10:19       ` Jan Kiszka
2012-01-09 11:07         ` Igor Mammedov [this message]
2012-01-09 11:15           ` Jan Kiszka

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=4F0ACA84.5050309@redhat.com \
    --to=imammedo@redhat.com \
    --cc=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=pingfank@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.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.