accel/kvm/kvm-all.c | 10 +++++++++- linux-headers/linux/kvm.h | 1 + monitor/hmp-cmds.c | 2 ++ qapi/stats.json | 4 +++- util/cutils.c | 4 ++++ util/oslib-posix.c | 4 ---- 6 files changed, 19 insertions(+), 6 deletions(-)
The following changes since commit 0ebf76aae58324b8f7bf6af798696687f5f4c2a9:
Merge tag 'nvme-next-pull-request' of git://git.infradead.org/qemu-nvme into staging (2022-07-15 15:38:13 +0100)
are available in the Git repository at:
https://gitlab.com/bonzini/qemu.git tags/for-upstream
for you to fetch changes up to 3746b8ca3e8bc216d03df5813080eeb06bdafabb:
util: Fix broken build on Haiku (2022-07-19 11:32:21 +0200)
----------------------------------------------------------------
* Boolean statistics for KVM
* Fix build on Haiku
----------------------------------------------------------------
Paolo Bonzini (2):
monitor: add support for boolean statistics
kvm: add support for boolean statistics
Thomas Huth (1):
util: Fix broken build on Haiku
accel/kvm/kvm-all.c | 10 +++++++++-
linux-headers/linux/kvm.h | 1 +
monitor/hmp-cmds.c | 2 ++
qapi/stats.json | 4 +++-
util/cutils.c | 4 ++++
util/oslib-posix.c | 4 ----
6 files changed, 19 insertions(+), 6 deletions(-)
--
2.36.1
On Tue, 19 Jul 2022 at 10:37, Paolo Bonzini <pbonzini@redhat.com> wrote: > > The following changes since commit 0ebf76aae58324b8f7bf6af798696687f5f4c2a9: > > Merge tag 'nvme-next-pull-request' of git://git.infradead.org/qemu-nvme into staging (2022-07-15 15:38:13 +0100) > > are available in the Git repository at: > > https://gitlab.com/bonzini/qemu.git tags/for-upstream > > for you to fetch changes up to 3746b8ca3e8bc216d03df5813080eeb06bdafabb: > > util: Fix broken build on Haiku (2022-07-19 11:32:21 +0200) > > ---------------------------------------------------------------- > * Boolean statistics for KVM > * Fix build on Haiku > Applied, thanks. Please update the changelog at https://wiki.qemu.org/ChangeLog/7.1 for any user-visible changes. -- PMM
Hi Paolo, On Tue, Jul 19, 2022 at 11:34:36AM +0200, Paolo Bonzini wrote: > The following changes since commit 0ebf76aae58324b8f7bf6af798696687f5f4c2a9: > > Merge tag 'nvme-next-pull-request' of git://git.infradead.org/qemu-nvme into staging (2022-07-15 15:38:13 +0100) > > are available in the Git repository at: > > https://gitlab.com/bonzini/qemu.git tags/for-upstream > > for you to fetch changes up to 3746b8ca3e8bc216d03df5813080eeb06bdafabb: > > util: Fix broken build on Haiku (2022-07-19 11:32:21 +0200) > > ---------------------------------------------------------------- > * Boolean statistics for KVM > * Fix build on Haiku > > ---------------------------------------------------------------- > Paolo Bonzini (2): > monitor: add support for boolean statistics > kvm: add support for boolean statistics > > Thomas Huth (1): > util: Fix broken build on Haiku > > accel/kvm/kvm-all.c | 10 +++++++++- > linux-headers/linux/kvm.h | 1 + > monitor/hmp-cmds.c | 2 ++ > qapi/stats.json | 4 +++- > util/cutils.c | 4 ++++ > util/oslib-posix.c | 4 ---- > 6 files changed, 19 insertions(+), 6 deletions(-) Considering the subject line, I'm quite distressed that the i386 setup_data rng seed patch did not make it in. I just resent it to the mailing list [1] in case you missed it before. Do you think you could queue this up ASAP? Thanks, Jason [1] https://lore.kernel.org/all/20220719115300.104095-1-Jason@zx2c4.com/
On 7/19/22 14:35, Jason A. Donenfeld wrote: >> 6 files changed, 19 insertions(+), 6 deletions(-) > Considering the subject line, I'm quite distressed that the i386 > setup_data rng seed patch did not make it in. I just resent it to the > mailing list [1] in case you missed it before. Do you think you could > queue this up ASAP? Sure, no problem. Unfortunately I was on vacation around the time you sent it first. Paolo
Hi Paolo, On Tue, Jul 19, 2022 at 8:15 PM Paolo Bonzini <pbonzini@redhat.com> wrote: > > On 7/19/22 14:35, Jason A. Donenfeld wrote: > >> 6 files changed, 19 insertions(+), 6 deletions(-) > > Considering the subject line, I'm quite distressed that the i386 > > setup_data rng seed patch did not make it in. I just resent it to the > > mailing list [1] in case you missed it before. Do you think you could > > queue this up ASAP? > > Sure, no problem. Unfortunately I was on vacation around the time you > sent it first. Excellent, thanks so much! Jason
Hey again, On Tue, Jul 19, 2022 at 08:15:54PM +0200, Jason A. Donenfeld wrote: > Hi Paolo, > > On Tue, Jul 19, 2022 at 8:15 PM Paolo Bonzini <pbonzini@redhat.com> wrote: > > > > On 7/19/22 14:35, Jason A. Donenfeld wrote: > > >> 6 files changed, 19 insertions(+), 6 deletions(-) > > > Considering the subject line, I'm quite distressed that the i386 > > > setup_data rng seed patch did not make it in. I just resent it to the > > > mailing list [1] in case you missed it before. Do you think you could > > > queue this up ASAP? > > > > Sure, no problem. Unfortunately I was on vacation around the time you > > sent it first. > > Excellent, thanks so much! Just wondering one thing: which tree did you put the patch in? I didn't see it on your gitlab, but it seems like QEMU development happens in many different places at once. Jason
On 7/20/22 13:20, Jason A. Donenfeld wrote: >>> Sure, no problem. Unfortunately I was on vacation around the time you >>> sent it first. >> Excellent, thanks so much! > Just wondering one thing: which tree did you put the patch in? I didn't > see it on your gitlab, but it seems like QEMU development happens in > many different places at once. Well, I still had to review it (unless I screw up, you get a reply from me once a patch is queued). I think there are some issues with migration compatibility of setup_data and they snowball a bit, so I'll reply there. Paolo
Hi Paolo, On Wed, Jul 20, 2022 at 02:47:48PM +0200, Paolo Bonzini wrote: > On 7/20/22 13:20, Jason A. Donenfeld wrote: > >>> Sure, no problem. Unfortunately I was on vacation around the time you > >>> sent it first. > >> Excellent, thanks so much! > > Just wondering one thing: which tree did you put the patch in? I didn't > > see it on your gitlab, but it seems like QEMU development happens in > > many different places at once. > > Well, I still had to review it (unless I screw up, you get a reply from > me once a patch is queued). I think there are some issues with > migration compatibility of setup_data and they snowball a bit, so I'll > reply there. Hmm, okay. Looking forward greatly to your reply there... Jason
© 2016 - 2024 Red Hat, Inc.