qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"blauwirbel@gmail.com" <blauwirbel@gmail.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"aurelien@aurel32.net" <aurelien@aurel32.net>
Subject: [Qemu-devel] Re: [PATCH v3 uq/master 00/22] Win32 iothread support
Date: Thu, 03 Mar 2011 11:12:06 +0200	[thread overview]
Message-ID: <4D6F5B66.1010004@redhat.com> (raw)
In-Reply-To: <4D6F5A38.1040209@siemens.com>

On 03/03/2011 11:07 AM, Jan Kiszka wrote:
> >
> >  Well that's strange, since qemu-kvm now passes autotest (and this was
> >  qemu.git + patchset, not qemu-kvm).
> >
>
> Does it fail every time? Have you tested if qemu.git also fails without
> the patches? Then we may have a chance to bisect.

I didn't check.  For extended testing it's better if Paolo or you get 
their own autotest setup.  I'm happy to run the occasional test for 
anyone but for digging in, it takes too much time and commits machine 
resources I need for other things.

Setting up autotest can be daunting, but the autotest people are *very* 
helpful.  I'm sure they'll be happy to hand-hold until you get things 
working.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2011-03-03  9:12 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28  9:10 [Qemu-devel] [PATCH v3 uq/master 00/22] Win32 iothread support Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 01/22] unlock iothread during WaitForMultipleObjects Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 02/22] implement win32 dynticks timer Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 03/22] use win32 timer queues Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 04/22] Refactor thread retrieval and check Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 05/22] add win32 qemu-thread implementation Paolo Bonzini
2011-02-28  9:33   ` [Qemu-devel] " Stefan Hajnoczi
2011-02-28 10:14     ` [Qemu-devel] [PATCH v4 uq/master] " Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 06/22] include qemu-thread.h early Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 07/22] add assertions on the owner of a QemuMutex Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 08/22] remove CONFIG_THREAD Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 09/22] target-sh4: move intr_at_halt out of cpu_halted() Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 10/22] inline cpu_halted into sole caller Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 11/22] always qemu_cpu_kick after unhalting a cpu Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 12/22] exit round-robin vcpu loop if cpu->stopped is true Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 13/22] always signal pause_cond after stopping a VCPU Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 14/22] do not use timedwait on qemu_halt_cond Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 15/22] do not use timedwait on qemu_system_cond Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 16/22] do not use timedwait on qemu_pause_cond Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 17/22] do not use timedwait on qemu_cpu_cond Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 18/22] iothread stops the vcpu thread via IPI Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 19/22] merge all signal initialization with qemu_signalfd_init, rename Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 20/22] provide dummy signal init functions for win32 Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 21/22] protect qemu_cpu_kick_self for Win32 Paolo Bonzini
2011-02-28  9:10 ` [Qemu-devel] [PATCH v3 uq/master 22/22] add Win32 IPI service Paolo Bonzini
2011-02-28  9:16 ` [Qemu-devel] Re: [PATCH v3 uq/master 00/22] Win32 iothread support Avi Kivity
2011-02-28 10:10   ` Paolo Bonzini
2011-02-28 11:57     ` Jan Kiszka
2011-02-28 12:13       ` Avi Kivity
2011-02-28 14:05         ` Paolo Bonzini
2011-03-01 12:35           ` Avi Kivity
2011-03-02 18:43             ` Marcelo Tosatti
2011-03-02 19:03               ` Jan Kiszka
2011-03-02 19:36                 ` Marcelo Tosatti
2011-03-02 19:42                   ` Marcelo Tosatti
2011-03-03  8:48                     ` Avi Kivity
2011-03-03  9:07                       ` Jan Kiszka
2011-03-03  9:12                         ` Avi Kivity [this message]
2011-03-03  9:13                         ` Paolo Bonzini
2011-03-03  9:28                           ` 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=4D6F5B66.1010004@redhat.com \
    --to=avi@redhat.com \
    --cc=aurelien@aurel32.net \
    --cc=blauwirbel@gmail.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.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).