kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Markus Armbruster <armbru@redhat.com>,
	Mark McLoughlin <markmc@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	kvm-devel <kvm@vger.kernel.org>,
	Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Planning for the 0.11.0 release
Date: Fri, 10 Jul 2009 11:33:13 -0500	[thread overview]
Message-ID: <4A576D49.40809@us.ibm.com> (raw)
In-Reply-To: <4A576AF6.6080307@siemens.com>

Jan Kiszka wrote:
> Ah, thanks.
>
> OK, then I would like to know the status of my -boot patch queue [1]

I'm stilling waiting for 1/7 and 2/7.  Via the link you posted and in my 
inbox, I still don't see those.  I do see a 1/2 and a 2/2 but those are 
bios patches.  Did you have a numbering issue or did some patches get 
lost in the ether?

>  and
> at least of patch 1..3 of my gdbstub queue [2] (though I'm still waiting
> for the factual proof that patch 4 is unneeded - my last arguments
> remained unanswered).
>   

Paul expressed objection in the past to the debugging model of treating 
vcpus as threads vs. treating them as processes.  I'm not qualified to 
appreciate the difference so I'm inclined to side with Paul.  Am I 
missing something there?

-- 
Regards,

Anthony Liguori


  reply	other threads:[~2009-07-10 16:33 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 23:57 Planning for the 0.11.0 release Anthony Liguori
2009-06-23 12:12 ` [Qemu-devel] " Avi Kivity
2009-06-23 15:09 ` Blue Swirl
2009-06-23 15:47   ` Anthony Liguori
2009-06-23 15:49   ` Avi Kivity
2009-07-09  8:27 ` Mark McLoughlin
2009-07-09 13:32   ` Anthony Liguori
2009-07-10  1:10     ` Markus Armbruster
2009-07-10 13:53       ` Anthony Liguori
2009-07-10 15:04         ` Jan Kiszka
2009-07-10 15:49           ` Anthony Liguori
2009-07-10 16:23             ` Jan Kiszka
2009-07-10 16:33               ` Anthony Liguori [this message]
2009-07-10 16:52                 ` Jan Kiszka
2009-07-10 17:03                   ` Anthony Liguori
2009-07-10 17:15                     ` Jan Kiszka
2009-07-10 17:40                     ` Paul Brook
2009-07-10 17:58                       ` Anthony Liguori
2009-07-10 18:02                       ` Jan Kiszka
2009-07-10 18:22                         ` Paul Brook
2009-07-10 16:55             ` Kevin Wolf
2009-07-10 16:59               ` Anthony Liguori
2009-07-10 17:10                 ` Kevin Wolf
2009-07-10 17:31                   ` Anthony Liguori
2009-07-10 17:10                 ` Christoph Hellwig
2009-07-10 17:12                   ` Kevin Wolf
2009-07-10 18:26                     ` Christoph Hellwig
2009-07-10 17:29                   ` Anthony Liguori
2009-07-10 18:13                     ` Christoph Hellwig
2009-07-10 18:29                       ` Anthony Liguori
2009-07-10 17:06               ` Anthony Liguori
2009-07-12  8:31                 ` Avi Kivity

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=4A576D49.40809@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=armbru@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=markmc@redhat.com \
    --cc=paul@codesourcery.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 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).