All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>, qemu-devel@nongnu.org
Subject: KVM call minutes July 10th
Date: Tue, 10 Jul 2012 16:55:32 +0200	[thread overview]
Message-ID: <874npfsm1n.fsf@elfo.mitica> (raw)


Hi

We discussed this

- cpu_index: is that transmited?  Yes (Juan).  we need to be sure that
  cpu_common and cpu use the same index/whatever it is changed

- We used cpu_index for SEABIOS interface as apic_id (Eduardo)

- cpu_hotplug makes that difficult.  How to pass the apic_id to
  seabios with cpu-hotplug?  Getting apic_id of a cpu without running
  code on that cpu is "tricky"  Anthony will look at the code.

- How to coordinate all changes with cpu hotplug?  Anthony and Andreas approach.
  * Andreas: move softmmu to DeviceState, and let linux-user use current object
  * Anthony1: use different structures for each
  * Anthony2: make linux-user also use DeviceState
  [long discussion here, that would be summarized by Andreas?]

Later, Juan.

WARNING: multiple messages have this Message-ID (diff)
From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>, qemu-devel@nongnu.org
Subject: [Qemu-devel] KVM call minutes July 10th
Date: Tue, 10 Jul 2012 16:55:32 +0200	[thread overview]
Message-ID: <874npfsm1n.fsf@elfo.mitica> (raw)


Hi

We discussed this

- cpu_index: is that transmited?  Yes (Juan).  we need to be sure that
  cpu_common and cpu use the same index/whatever it is changed

- We used cpu_index for SEABIOS interface as apic_id (Eduardo)

- cpu_hotplug makes that difficult.  How to pass the apic_id to
  seabios with cpu-hotplug?  Getting apic_id of a cpu without running
  code on that cpu is "tricky"  Anthony will look at the code.

- How to coordinate all changes with cpu hotplug?  Anthony and Andreas approach.
  * Andreas: move softmmu to DeviceState, and let linux-user use current object
  * Anthony1: use different structures for each
  * Anthony2: make linux-user also use DeviceState
  [long discussion here, that would be summarized by Andreas?]

Later, Juan.

             reply	other threads:[~2012-07-10 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10 14:55 Juan Quintela [this message]
2012-07-10 14:55 ` [Qemu-devel] KVM call minutes July 10th Juan Quintela
2012-07-10 17:24 ` Andreas Färber
2012-07-10 17:24   ` Andreas Färber

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=874npfsm1n.fsf@elfo.mitica \
    --to=quintela@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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.