From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Graf <agraf@suse.de>
Cc: "Avi Kivity" <avi@redhat.com>,
"Anthony Liguori" <anthony@codemonkey.ws>,
"Andreas Färber" <afaerber@suse.de>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>
Subject: Re: [Qemu-devel] [PULL 00/20 1.2] kvm updates
Date: Tue, 05 Jun 2012 08:32:37 +0000 [thread overview]
Message-ID: <4FCDC425.4010609@siemens.com> (raw)
In-Reply-To: <74F64445-779D-4F48-B043-0AB8F2E55B26@suse.de>
On 2012-06-05 10:10, Alexander Graf wrote:
>
>
> On 05.06.2012, at 09:42, Avi Kivity <avi@redhat.com> wrote:
>
>> On 06/05/2012 04:58 AM, Anthony Liguori wrote:
>>> On 06/05/2012 08:52 AM, Andreas Färber wrote:
>>>> Am 04.06.2012 07:46, schrieb Anthony Liguori:
>>>>> On 05/22/2012 12:37 AM, Avi Kivity wrote:
>>>>>> Please pull from:
>>>>>>
>>>>>> git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git uq/master
>>>>>
>>>>> Pulled. Thanks.
>>>>
>>>> This broke the ppc build. Guys, why wasn't this tested? There's only
>>>> three KVM targets to test compared to the 14 I'm struggling with...
>>>
>>> Is build bot running against uq/master? If it's not, maybe we should
>>> add it to build bot to catch this sort of thing.
>>
>> A build bot is overkill. I usually do a full build (and autotest),
>> don't know how this was missed.
>
> Not sure why it would be overkill. We have build bots running on more exotic hw (ppc and s390) with kvm available for that exact purpose. They're running either way - all we need to do is enable uq/master and we catch these before the next pull request :).
I think this makes some sense. uq/master is supposed to be the staging
branch for generic and (at least) x86 kvm changes in QEMU. So it should
cover at least their builds.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Graf <agraf@suse.de>
Cc: "Avi Kivity" <avi@redhat.com>,
"Anthony Liguori" <anthony@codemonkey.ws>,
"Andreas Färber" <afaerber@suse.de>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>
Subject: Re: [Qemu-devel] [PULL 00/20 1.2] kvm updates
Date: Tue, 05 Jun 2012 10:32:37 +0200 [thread overview]
Message-ID: <4FCDC425.4010609@siemens.com> (raw)
In-Reply-To: <74F64445-779D-4F48-B043-0AB8F2E55B26@suse.de>
On 2012-06-05 10:10, Alexander Graf wrote:
>
>
> On 05.06.2012, at 09:42, Avi Kivity <avi@redhat.com> wrote:
>
>> On 06/05/2012 04:58 AM, Anthony Liguori wrote:
>>> On 06/05/2012 08:52 AM, Andreas Färber wrote:
>>>> Am 04.06.2012 07:46, schrieb Anthony Liguori:
>>>>> On 05/22/2012 12:37 AM, Avi Kivity wrote:
>>>>>> Please pull from:
>>>>>>
>>>>>> git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git uq/master
>>>>>
>>>>> Pulled. Thanks.
>>>>
>>>> This broke the ppc build. Guys, why wasn't this tested? There's only
>>>> three KVM targets to test compared to the 14 I'm struggling with...
>>>
>>> Is build bot running against uq/master? If it's not, maybe we should
>>> add it to build bot to catch this sort of thing.
>>
>> A build bot is overkill. I usually do a full build (and autotest),
>> don't know how this was missed.
>
> Not sure why it would be overkill. We have build bots running on more exotic hw (ppc and s390) with kvm available for that exact purpose. They're running either way - all we need to do is enable uq/master and we catch these before the next pull request :).
I think this makes some sense. uq/master is supposed to be the staging
branch for generic and (at least) x86 kvm changes in QEMU. So it should
cover at least their builds.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Graf <agraf@suse.de>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>,
"Avi Kivity" <avi@redhat.com>,
"Anthony Liguori" <anthony@codemonkey.ws>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PULL 00/20 1.2] kvm updates
Date: Tue, 05 Jun 2012 10:32:37 +0200 [thread overview]
Message-ID: <4FCDC425.4010609@siemens.com> (raw)
In-Reply-To: <74F64445-779D-4F48-B043-0AB8F2E55B26@suse.de>
On 2012-06-05 10:10, Alexander Graf wrote:
>
>
> On 05.06.2012, at 09:42, Avi Kivity <avi@redhat.com> wrote:
>
>> On 06/05/2012 04:58 AM, Anthony Liguori wrote:
>>> On 06/05/2012 08:52 AM, Andreas Färber wrote:
>>>> Am 04.06.2012 07:46, schrieb Anthony Liguori:
>>>>> On 05/22/2012 12:37 AM, Avi Kivity wrote:
>>>>>> Please pull from:
>>>>>>
>>>>>> git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git uq/master
>>>>>
>>>>> Pulled. Thanks.
>>>>
>>>> This broke the ppc build. Guys, why wasn't this tested? There's only
>>>> three KVM targets to test compared to the 14 I'm struggling with...
>>>
>>> Is build bot running against uq/master? If it's not, maybe we should
>>> add it to build bot to catch this sort of thing.
>>
>> A build bot is overkill. I usually do a full build (and autotest),
>> don't know how this was missed.
>
> Not sure why it would be overkill. We have build bots running on more exotic hw (ppc and s390) with kvm available for that exact purpose. They're running either way - all we need to do is enable uq/master and we catch these before the next pull request :).
I think this makes some sense. uq/master is supposed to be the staging
branch for generic and (at least) x86 kvm changes in QEMU. So it should
cover at least their builds.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-06-05 8:32 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 16:37 [PULL 00/20 1.2] kvm updates Avi Kivity
2012-05-21 16:37 ` [Qemu-devel] " Avi Kivity
2012-05-21 16:37 ` [PATCH 01/19] kvm: Refactor KVMState::max_gsi to gsi_count Avi Kivity
2012-05-21 16:37 ` [Qemu-devel] " Avi Kivity
2012-05-21 16:37 ` [PATCH 02/19] Introduce MSIMessage structure Avi Kivity
2012-05-21 16:37 ` [Qemu-devel] " Avi Kivity
2012-05-21 16:37 ` [PATCH 03/19] kvm: Introduce basic MSI support for in-kernel irqchips Avi Kivity
2012-05-21 16:37 ` [Qemu-devel] " Avi Kivity
2012-05-21 16:37 ` [PATCH 04/19] pc: Enable MSI support at APIC level Avi Kivity
2012-05-21 16:37 ` [Qemu-devel] " Avi Kivity
2012-05-21 16:37 ` [PATCH 05/19] kvm: x86: Wire up MSI support for in-kernel irqchip Avi Kivity
2012-05-21 16:37 ` [Qemu-devel] " Avi Kivity
2012-05-21 16:37 ` [PATCH 06/19] kvm: Update kernel headers Avi Kivity
2012-05-21 16:37 ` [Qemu-devel] " Avi Kivity
2012-05-21 16:37 ` [PATCH 07/19] kvm: Add support for direct MSI injections Avi Kivity
2012-05-21 16:37 ` [Qemu-devel] " Avi Kivity
2012-05-21 16:37 ` [PATCH 08/19] kvm: Enable in-kernel irqchip support by default Avi Kivity
2012-05-21 16:37 ` [Qemu-devel] " Avi Kivity
2012-05-21 16:37 ` [PATCH 09/19] msix: Factor out msix_get_message Avi Kivity
2012-05-21 16:37 ` [Qemu-devel] " Avi Kivity
2012-05-21 16:37 ` [PATCH 10/19] msix: Invoke msix_handle_mask_update on msix_mask_all Avi Kivity
2012-05-21 16:37 ` [Qemu-devel] " Avi Kivity
2012-05-21 16:37 ` [PATCH 11/19] msix: Introduce vector notifiers Avi Kivity
2012-05-21 16:37 ` [Qemu-devel] " Avi Kivity
2012-05-21 16:37 ` [PATCH 12/19] kvm: Rename kvm_irqchip_add_route to kvm_irqchip_add_irq_route Avi Kivity
2012-05-21 16:37 ` [Qemu-devel] " Avi Kivity
2012-05-21 16:37 ` [PATCH 13/19] kvm: Introduce kvm_irqchip_add_msi_route Avi Kivity
2012-05-21 16:37 ` [Qemu-devel] " Avi Kivity
2012-05-21 16:37 ` [PATCH 14/19] kvm: Publicize kvm_irqchip_release_virq Avi Kivity
2012-05-21 16:37 ` [Qemu-devel] " Avi Kivity
2012-05-21 16:37 ` [PATCH 15/19] kvm: Make kvm_irqchip_commit_routes an internal service Avi Kivity
2012-05-21 16:37 ` [Qemu-devel] " Avi Kivity
2012-05-21 16:37 ` [PATCH 16/19] kvm: Introduce kvm_irqchip_add/remove_irqfd Avi Kivity
2012-05-21 16:37 ` [Qemu-devel] " Avi Kivity
2012-05-21 16:37 ` [PATCH 17/19] kvm: Enable use of kvm_irqchip_in_kernel in hwlib code Avi Kivity
2012-05-21 16:37 ` [Qemu-devel] " Avi Kivity
2012-05-21 16:37 ` [PATCH 18/19] msix: Add msix_nr_vectors_allocated Avi Kivity
2012-05-21 16:37 ` [Qemu-devel] " Avi Kivity
2012-05-21 16:37 ` [PATCH 19/19] virtio/vhost: Add support for KVM in-kernel MSI injection Avi Kivity
2012-05-21 16:37 ` [Qemu-devel] " Avi Kivity
2012-06-04 5:46 ` [Qemu-devel] [PULL 00/20 1.2] kvm updates Anthony Liguori
2012-06-05 0:52 ` Andreas Färber
2012-06-05 0:52 ` Andreas Färber
2012-06-05 0:52 ` Andreas Färber
2012-06-05 1:58 ` Anthony Liguori
2012-06-05 1:58 ` Anthony Liguori
2012-06-05 1:58 ` Anthony Liguori
2012-06-05 2:26 ` Andreas Färber
2012-06-05 2:26 ` Andreas Färber
2012-06-05 2:26 ` Andreas Färber
2012-06-05 7:42 ` Avi Kivity
2012-06-05 7:42 ` Avi Kivity
2012-06-05 7:42 ` Avi Kivity
2012-06-05 8:10 ` Alexander Graf
2012-06-05 8:10 ` Alexander Graf
2012-06-05 8:10 ` Alexander Graf
2012-06-05 8:32 ` Jan Kiszka [this message]
2012-06-05 8:32 ` [Qemu-devel] " Jan Kiszka
2012-06-05 8:32 ` Jan Kiszka
2012-06-05 9:02 ` Anthony Liguori
2012-06-05 9:02 ` Anthony Liguori
2012-06-05 9:11 ` Avi Kivity
2012-06-05 9:11 ` Avi Kivity
2012-06-05 9:11 ` 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=4FCDC425.4010609@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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 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.