The new property ibm,dynamic-memory-v2 allows memory to be represented
in a more compact manner in device tree.
Signed-off-by: Bharata B Rao
---
v3: https://lists.gnu.org/archive/html/qemu-devel/2018-04/msg02159.html
Changes in v4: (Addresses all David Gibson's comments)
- Use of QEMU_PACKED for
Marc-André Lureau writes:
> Hi,
>
> This series aims to get rid of the distinction between QObject, that
> must use qobject_incref/qobject_decref and its various derived types
> that have to use QINCREF/QDECREF. Instead, replace it with
> qobject_ref/qobject_unref for all types.
This is a lovely
The way the POWER Hash Page Table (HPT) MMU is virtualized by KVM HV means
that every page that the guest puts in the pagetables must be truly
physically contiguous, not just GPA-contiguous. In effect this means that
an HPT guest can't use any pagesizes greater than the host page size used
to back
Currently during KVM initialization on POWER, kvm_fixup_page_sizes()
rewrites a bunch of information in the cpu state to reflect the
capabilities of the host MMU and KVM. This overwrites the information
that's already there reflecting how the TCG implementation of the MMU will
operate.
This means
spapr capabilities have an apply hook to actually activate (or deactivate)
the feature in the system at reset time. However, a number of capabilities
affect the setup of cpus, and need to be applied to each of them -
including hotplugged cpus for extra complication. To make this simpler,
add an o
KVM HV has some limitations (deriving from the hardware) that mean not all
host-cpu supported pagesizes may be usable in the guest. At present this
means that KVM guests and TCG guests may see different available page sizes
even if they notionally have the same vcpu model. This is confusing and
a
The paravirtualized PAPR platform sometimes needs to restrict the guest to
using only some of the page sizes actually supported by the host's MMU.
At the moment this is handled in KVM specific code, but for consistency we
want to apply the same limitations to all accelerators.
This makes a start o
The way we used to handle KVM allowable guest pagesizes for PAPR guests
required some convoluted checking of memory attached to the guest.
The allowable pagesizes advertised to the guest cpus depended on the memory
which was attached at boot, but then we needed to ensure that any memory
later hotp
By default, the IOMMU model built into the spapr virtual PCI host bridge
supports 4kiB and 64kiB IOMMU page sizes. However this can be overridden
which may be desirable to allow larger IOMMU page sizes when running a
guest with hugepage backing and passthrough devices. For that reason a
warning w
Currently the "pseries" machine type will (usually) advertise
different pagesizes to the guest when running under KVM and TCG, which
is not how things are supposed to work.
This comes from poor handling of hardware limitations which mean that
under KVM HV the guest is unable to use pagesizes large
SNOOP_NONE state handle is moved above in the if ladder, as it's same
as SNOOP_STRIPPING during data cycles.
Signed-off-by: Sai Pavan Boddu
---
Changes for V2:
Fixed commit message
Reordered to code, to avoid code duplication.
Changes for V3:
Dropped the cover letter, as i
Eric Blake writes:
> On 04/17/2018 08:36 AM, Marc-André Lureau wrote:
>> For convenience and clarity, make it possible to call qobject_ref() at
>> the time when the reference is associated with a variable, or
>> argument, by making qobject_ref() return the same pointer as given.
>>
>> Signed-off
Marc-André Lureau writes:
> While it may be convenient to accept NULL value in
> qobject_unref() (for similar reasons as free() accepts NULL), it is
> not such a good idea for qobject_ref(), assert() on NULL. One place
> relied on that behaviour (the monitor request id), and it's best to be
> exp
Marc-André Lureau writes:
> Now that we can safely call QOBJECT() on QObject * as well as its
> subtypes, we can have macros qobject_ref() / qobject_unref() that work
> everywhere instead of having to use QINCREF() / QDECREF() for QObject
> and qobject_incref() / qobject_decref() for its subtypes
In addition to Eric's comments...
Marc-André Lureau writes:
> By moving the base fields to a QObjectBase_, QObject can be a type
> which also has a 'base' field. This allows to write a generic
> QOBJECT() macro that will work with any QObject type, including
> QObject itself. The container_of()
Eric Blake writes:
> On 04/18/2018 11:45 AM, Markus Armbruster wrote:
>
>>> Might also be worth mentioning that this explicitly guarantees that
>>> existing casts work correctly (even though we'd prefer to get rid of
>>> such casts in any location except the qobject.h macros); Markus pointed out:
HI Franciso,
From: francisco iglesias [mailto:frasse.igles...@gmail.com]
Sent: Thursday, April 19, 2018 3:39 AM
To: Sai Pavan Boddu
Cc: alist...@alistair23.me; Peter Crosthwaite ;
Peter Maydell ; Edde ;
qemu-devel@nongnu.org Developers
Subject: Re: [Qemu-devel] [PATCH v2 1/1] xilinx_spips: sen
On 18.04.2018 20:21, Farhan Ali wrote:
> On 04/18/2018 08:31 AM, Thomas Huth wrote:
>> Some patches to improve the network boot experience on s390x:
>>
>> First, make sure that we shut down the virtio-net device before jumping
>> into the kernel. Otherwise some incoming packets might destroy some o
On 18.04.2018 20:11, Farhan Ali wrote:
>
>
> On 04/18/2018 08:31 AM, Thomas Huth wrote:
>> When we want to support pxelinux-style network booting later, we've got
>> to do several TFTP transfers - and we do not want to apply for a new IP
>> address via DHCP each time. So split up net_load into th
On 19.04.2018 04:06, Fam Zheng wrote:
> On Mon, 04/16 16:09, Markus Armbruster wrote:
>> Thomas Huth writes:
>>
>>> On 12.03.2018 14:18, Stefan Hajnoczi wrote:
Warn if files are added/renamed/deleted without MAINTAINERS file
changes. This has helped me in Linux and we could benefit from
On Wed, Apr 18, 2018 at 09:36:33AM +0100, Dr. David Alan Gilbert wrote:
> * Balamuruhan S (bal...@linux.vnet.ibm.com) wrote:
> > On Wed, Apr 18, 2018 at 10:57:26AM +1000, David Gibson wrote:
> > > On Wed, Apr 18, 2018 at 10:55:50AM +1000, David Gibson wrote:
> > > > On Tue, Apr 17, 2018 at 06:53:17
Hi Zong,
> On 19/04/2018, at 2:40 PM, Zong Li wrote:
>
> Hi all,
>
> For BBL part, in fp_init at machine/minit.c,
> it will clear the D and F bits of misa register, and assertion that
> the bits is cleared.
> But the misa is WARL register, so there is no effect for writing it,
> and the asserti
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1708077
Title:
PPC interru
On Wed, Apr 18, 2018 at 04:28:02PM +0200, Igor Mammedov wrote:
> Convert PPCE500Params to PCCE500MachineClass which it essentially is,
> and introduce PCCE500MachineState to keep track of E500 specific
> state instead of adding global variables or extra parameters to
> functions when we need to kee
在 2018/4/13 16:05, Perez Blanco, Ricardo (Nokia - BE/Antwerp) 写道:
> Dear all,
>
> Here you can find my first contribution to qemu. Please, do not hesitate to
> do any kind of remark.
>
> Based on ac4ba87ae0738d7a77708f8ce31ae2378ab99654
>
> Kind regards,
>
> Ricardo Perez Blanco
>
>>From 65
在 2018/4/18 22:04, Dr. David Alan Gilbert 写道:
> * QingFeng Hao (ha...@linux.vnet.ibm.com) wrote:
>> Hi all,
>> I did some investigation and found that "virsh qemu-monitor-command"
>> supports qom-get,
>> but qemu hmp doesn't. However, in hmp.c there are qom_list and qom_set. It
>> confused me
>
On Thu, Apr 19, 2018 at 09:56:31AM +0800, Fam Zheng wrote:
> On Wed, 04/18 17:06, Peter Xu wrote:
> > We have had some tracing tools for mutex but it's not easy to use them
> > for e.g. dead locks. Let's provide "--enable-debug-mutex" parameter
> > when configure to allow QemuMutex to store the la
On 12/4/18 7:15 pm, Paolo Bonzini wrote:
> On 29/03/2018 05:21, Alexey Kardashevskiy wrote:
>> +DeviceState *dev = (DeviceState *) object_dynamic_cast(obj,
>> TYPE_DEVICE);
>> +const char *id = object_property_print(obj, "id", true, NULL);
>
> I learnt now about commit e1ff3c67e8544f41f1b
On Mon, 04/16 16:09, Markus Armbruster wrote:
> Thomas Huth writes:
>
> > On 12.03.2018 14:18, Stefan Hajnoczi wrote:
> >> Warn if files are added/renamed/deleted without MAINTAINERS file
> >> changes. This has helped me in Linux and we could benefit from this
> >> check in QEMU.
> >>
> >> This
On Wed, 04/18 17:06, Peter Xu wrote:
> We have had some tracing tools for mutex but it's not easy to use them
> for e.g. dead locks. Let's provide "--enable-debug-mutex" parameter
> when configure to allow QemuMutex to store the last owner that took
> specific lock. It might be extremely easy to
On 04/18/2018 09:06 PM, Max Reitz wrote:
On 2018-04-16 09:46, zhenwei pi wrote:
currently qemu progress message only print into stdout, and other thread may
print some log into stdout at the same time.
add a new api qemu_progress_set_output to redirect progress message to
another file stream.
On Wed, 18 Apr 2018 10:32:06 +0200
Laszlo Ersek wrote:
> On 04/18/18 08:02, Gerd Hoffmann wrote:
> [...]
> [...]
> >
> > Looks good to me overall.
> >
> >> +{ 'enum' : 'FirmwareType',
> >> + 'data' : [ 'bios', 'slof', 'uboot', 'uefi' ] }
> >
> > openbios missing.
> >
> >> +{ 'enum' :
Hi Sai,
About the subject, what do you think about changing it to below?
xilinx_spips: Correct SNOOP_NONE state when flushing the txfifo
On 18 April 2018 at 09:41, Sai Pavan Boddu
wrote:
> For all the commands, which do not have an entry in
> xilinx_spips_num_dummies, present logic sends dummy
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180418123838.3511-1-o...@aepfle.de
Subject: [Qemu-devel] [PATCH v1] configure: require
Hi,
FYI
100% cpu usage on kernel 4.15.8
coreduo 2 cores, address sizes 0 bits virtual.
no problem with qemu cpu 2.5+.
regards,
jfm
On 04/18/2018 08:31 AM, Thomas Huth wrote:
Some patches to improve the network boot experience on s390x:
First, make sure that we shut down the virtio-net device before jumping
into the kernel. Otherwise some incoming packets might destroy some of
the kernel's data if it has not taken over the
On 04/18/2018 08:31 AM, Thomas Huth wrote:
When we want to support pxelinux-style network booting later, we've got
to do several TFTP transfers - and we do not want to apply for a new IP
address via DHCP each time. So split up net_load into three parts:
1. net_init(), which initializes virtio-
On Wed, 18 Apr 2018 18:11:51 +0100
Daniel P. Berrangé wrote:
> The "git archive" feature creates tarballs which are missing all
> submodule content. GitHub unhelpfully provides users with "Download"
> links that claim to give them valid source release tarballs. These
> GitHub archives will not be
On Tue, 17 Apr 2018 21:58:21 +0300
"Michael S. Tsirkin" wrote:
> It turns out (as will be clear from follow-up patches)
> we do not really need any kvm para macros host side
> for now, except on x86, and there we need it
> unconditionally whether we run on kvm or we don't.
>
> Import the x86 asm
John Snow writes:
> On 04/18/2018 03:25 AM, Markus Armbruster wrote:
>> John Snow writes:
>>
>>> On 04/17/2018 09:44 AM, Markus Armbruster wrote:
John Snow writes:
> This series seeks to address two distinct but closely related issues
> concerning the job management API.
On Wed, 18 Apr 2018 19:05:15 +0300
"Michael S. Tsirkin" wrote:
> On Wed, Apr 18, 2018 at 09:54:26AM +0200, Cornelia Huck wrote:
> > On Tue, 17 Apr 2018 21:58:21 +0300
> > "Michael S. Tsirkin" wrote:
> >
> > > It turns out (as will be clear from follow-up patches)
> > > we do not really need a
This patch adds Windows crashdumping feature. Now QEMU can produce ELF-dump
containing Windows crashdump header, which can help to convert to a valid
WinDbg-understandable crashdump file, or immediately create such file.
The crashdump will be obtained by joining physical memory dump and 8K header
e
On 04/18/2018 03:25 AM, Markus Armbruster wrote:
> John Snow writes:
>
>> On 04/17/2018 09:44 AM, Markus Armbruster wrote:
>>> John Snow writes:
>>>
This series seeks to address two distinct but closely related issues
concerning the job management API.
(1) For jobs that com
The "git archive" feature creates tarballs which are missing all
submodule content. GitHub unhelpfully provides users with "Download"
links that claim to give them valid source release tarballs. These
GitHub archives will not be buildable as they are created by the
"git archive" feature and so are
On Wed, Apr 18, 2018 at 06:52:08PM +0200, Kevin Wolf wrote:
> Am 18.04.2018 um 18:34 hat Daniel P. Berrangé geschrieben:
> > On Wed, Apr 18, 2018 at 06:28:23PM +0200, Kevin Wolf wrote:
> > > Am 18.04.2018 um 17:06 hat Markus Armbruster geschrieben:
> >
> > > > Note that users can still configu
On 04/18/2018 11:45 AM, Markus Armbruster wrote:
>> Might also be worth mentioning that this explicitly guarantees that
>> existing casts work correctly (even though we'd prefer to get rid of
>> such casts in any location except the qobject.h macros); Markus pointed out:
>>
Uh, there's anothe
Hi
On Wed, Apr 18, 2018 at 6:45 PM, Markus Armbruster wrote:
> Eric Blake writes:
>
>> On 04/17/2018 08:35 AM, Marc-André Lureau wrote:
>>> All QObject types have the base QObject as first field. This allows to
>>
>> s/as/as their/
>>
>>> simplify qobject_to() and will allow further simplificati
Am 18.04.2018 um 18:34 hat Daniel P. Berrangé geschrieben:
> On Wed, Apr 18, 2018 at 06:28:23PM +0200, Kevin Wolf wrote:
> > Am 18.04.2018 um 17:06 hat Markus Armbruster geschrieben:
>
> > > Note that users can still configure authentication methods with a
> > > configuration file. They p
Eric Blake writes:
> On 04/17/2018 08:35 AM, Marc-André Lureau wrote:
>> All QObject types have the base QObject as first field. This allows to
>
> s/as/as their/
>
>> simplify qobject_to() and will allow further simplification in
>
> s/allows to simplify/allows the simplification of/
> s/in/in t
On 04/13/2018 09:31 AM, Vladimir Sementsov-Ogievskiy wrote:
> Handle nbd CACHE command. Just do read, without sending read data back.
> Cache mechanism should be done by exported node driver chain.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> ---
> include/block/nbd.h | 3 ++-
> nbd/server
On 03/02/2018 06:25 PM, Alexey Kardashevskiy wrote:
> ObjectPropertyInfo is more generic and only missing @description.
> This adds a description to ObjectPropertyInfo and removes
> DevicePropertyInfo so the resulting ObjectPropertyInfo can be used
> elsewhere.
>
> Signed-off-by: Alexey Kardashevs
On Wed, Apr 18, 2018 at 06:28:23PM +0200, Kevin Wolf wrote:
> Am 18.04.2018 um 17:06 hat Markus Armbruster geschrieben:
> > Note that users can still configure authentication methods with a
> > configuration file. They probably do that anyway if they use Ceph
> > outside QEMU as well.
On Thu, Apr 12, 2018 at 11:12:32PM +0800, Tiwei Bie wrote:
> This patch introduces VHOST_USER_PROTOCOL_F_HOST_NOTIFIER.
> With this feature negotiated, vhost-user backend can register
> memory region based host notifiers. And it will allow the guest
> driver in the VM to notify the hardware acceler
On 04/18/2018 11:28 AM, Igor Mammedov wrote:
> platform-bus were using machine_done notifier to get and map
> (assign irq/mmio resources) dynamically added sysbus devices
> after all '-device' options had been processed.
> That however creates non obvious dependencies on ordering of
> machine_done
Am 18.04.2018 um 17:06 hat Markus Armbruster geschrieben:
> Kevin Wolf writes:
>
> > The legacy command line syntax supports a "password-secret" option that
> > allows to pass an authentication key to Ceph. This was not supported in
> > QMP so far.
>
> We tried during development of v2.9.0 (comm
On 04/18/2018 11:28 AM, Igor Mammedov wrote:
> if arm_load_kernel() were passed non first_cpu, QEMU would end up
> with partially set do_cpu_reset() callback leaving some CPUs without it.
>
> Make sure that do_cpu_reset() is registered for all CPUs by enumerating
> CPUs from first_cpu.
>
> Signed
On 04/18/2018 11:56 AM, Eduardo Habkost wrote:
> On Wed, Apr 18, 2018 at 04:28:03PM +0200, Igor Mammedov wrote:
>> By default MachineClass::get_hotplug_handler is NULL and concrete board
>> should set it to it's own handler.
>> Considering there isn't any default handler, drop saving empty
>> Machi
Looking through old bug tickets... can you still reproduce this issue
with the latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribe
Looking through old bug tickets... can you still reproduce this issue
with the latest version of QEMU and a recent guest kernel? Or could we
close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
de
Looking through old bug tickets... can you still reproduce this issue
with the latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribe
Looking through old bug tickets... can you still reproduce this issue
with the latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribe
On Wed, Apr 18, 2018 at 09:54:26AM +0200, Cornelia Huck wrote:
> On Tue, 17 Apr 2018 21:58:21 +0300
> "Michael S. Tsirkin" wrote:
>
> > It turns out (as will be clear from follow-up patches)
> > we do not really need any kvm para macros host side
> > for now, except on x86, and there we need it
>
On 18/04/2018 16:54, Olaf Hering wrote:
> Since usage of g_realloc_n was introduced, glib-2.22 can not be used
> anymore on Linux. Leave non-Linux unchanged because one developer system
> still uses it.
> Fixes commit 418026ca43 ("util: Introduce vfio helpers")
>
> Signed-off-by: Olaf Hering
> --
Am Wed, 18 Apr 2018 10:04:03 -0500
schrieb Eric Blake :
> avoid g_realloc_n()?
I guess there is some global header for this, to prevent further accidents?
extern void *g_realloc_n_can_not_be_used(void);
#define g_realloc_n(a,b,c) g_realloc_n_can_not_be_used()
Olaf
pgp_y86xwZs_3.pgp
Descripti
On Mon 16 Apr 2018 05:15:21 PM CEST, Max Reitz wrote:
> On 2018-04-16 16:59, Alberto Garcia wrote:
>> On Fri 13 Apr 2018 04:23:07 PM CEST, Max Reitz wrote:
>>> On 2018-04-12 19:07, Alberto Garcia wrote:
Hello,
I mentioned this some time ago, but I'd like to retake it now: I'm
ch
Am Wed, 18 Apr 2018 10:04:03 -0500
schrieb Eric Blake :
> Rather than hacking configure, why not fix util/vfio-helpers.c to avoid
> g_realloc_n()? We've done it before; see commit 071d405
I can not really test it, this variant may work:
--- a/util/vfio-helpers.c
+++ b/util/vfio-helpers.c
@@ -52
On 04/18/18 17:27, Laszlo Ersek wrote:
> On 04/18/18 17:17, Eric Blake wrote:
>> On 04/18/2018 07:40 AM, Laszlo Ersek wrote:
>>
>>> Is it guaranteed that lists in JSON keep the order of the elements?
>>> Because, dictionaries definitely don't promise any ordering between the
>>> keys.
>>
>> Yes, JS
On Wed, Apr 18, 2018 at 05:27:32PM +0200, Laszlo Ersek wrote:
> On 04/18/18 17:17, Eric Blake wrote:
> > On 04/18/2018 07:40 AM, Laszlo Ersek wrote:
> >
> >> Is it guaranteed that lists in JSON keep the order of the elements?
> >> Because, dictionaries definitely don't promise any ordering between
On 04/18/18 17:17, Eric Blake wrote:
> On 04/18/2018 07:40 AM, Laszlo Ersek wrote:
>
>> Is it guaranteed that lists in JSON keep the order of the elements?
>> Because, dictionaries definitely don't promise any ordering between the
>> keys.
>
> Yes, JSON lists preserve order (and we have to explic
On 04/18/2018 07:40 AM, Laszlo Ersek wrote:
> Is it guaranteed that lists in JSON keep the order of the elements?
> Because, dictionaries definitely don't promise any ordering between the
> keys.
Yes, JSON lists preserve order (and we have to explicitly document cases
where order within a list is
Kevin Wolf writes:
> The legacy command line syntax supports a "password-secret" option that
> allows to pass an authentication key to Ceph. This was not supported in
> QMP so far.
We tried during development of v2.9.0 (commit 0a55679b4a5), but reverted
before the release:
commit 46fcc16128
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180418145443.6332-1-o...@aepfle.de
Subject: [Qemu-devel] [PATCH v2] configure: require
On 04/18/2018 09:54 AM, Olaf Hering wrote:
> Since usage of g_realloc_n was introduced, glib-2.22 can not be used
> anymore on Linux. Leave non-Linux unchanged because one developer system
> still uses it.
> Fixes commit 418026ca43 ("util: Introduce vfio helpers")
>
> Signed-off-by: Olaf Hering
>
On Wed, Apr 18, 2018 at 04:28:03PM +0200, Igor Mammedov wrote:
> By default MachineClass::get_hotplug_handler is NULL and concrete board
> should set it to it's own handler.
> Considering there isn't any default handler, drop saving empty
> MachineClass::get_hotplug_handler in child class and make
Hello,
On behalf of the QEMU Team, I'd like to announce the availability of the
fifth release candidate for the QEMU 2.12 release. This release is meant
for testing purposes and should not be used in a production environment.
http://download.qemu-project.org/qemu-2.12.0-rc4.tar.xz
http://dow
Since usage of g_realloc_n was introduced, glib-2.22 can not be used
anymore on Linux. Leave non-Linux unchanged because one developer system
still uses it.
Fixes commit 418026ca43 ("util: Introduce vfio helpers")
Signed-off-by: Olaf Hering
---
configure | 6 +-
1 file changed, 5 insertions(
On 04/17/2018 08:50 AM, Viktor Prutyanov wrote:
> This patch adds Windows crashdumping feature. Now QEMU can produce ELF-dump
> containing Windows crashdump header, which can help to convert to a valid
> WinDbg-understandable crashdump file, or immediately create such file.
> The crashdump will be
Am Wed, 18 Apr 2018 14:45:38 +0200
schrieb Cornelia Huck :
> Are we ready to give up support for whatever distro is still on 2.22?
This is SLE11, in case it matters for this discussion.
Olaf
pgp5sY4ljZvqS.pgp
Description: Digitale Signatur von OpenPGP
On 04/18/18 16:06, Daniel P. Berrangé wrote:
> On Wed, Apr 18, 2018 at 04:03:03PM +0200, Laszlo Ersek wrote:
>> - Would you like me to capture the directory paths in the firmware.json
>> file, or in the commit message for the patch?
>
> Should be in whatever file ends up in the docs/specs direc
On Wed, Apr 18, 2018 at 02:29:47PM +0100, Peter Maydell wrote:
> On 18 April 2018 at 13:47, Daniel P. Berrangé wrote:
> > On Wed, Apr 18, 2018 at 02:38:37PM +0200, Olaf Hering wrote:
> >> Since usage of g_realloc_n was introduced, glib-2.22 can not be used
> >> anymore.
> >> Fixes commit 418026ca
On Wed, Apr 18, 2018 at 04:41:39PM +0200, Cornelia Huck wrote:
> On Wed, 18 Apr 2018 13:55:45 +0100
> Daniel P. Berrangé wrote:
>
> > On Wed, Apr 18, 2018 at 02:45:38PM +0200, Cornelia Huck wrote:
> > > On Wed, 18 Apr 2018 14:38:37 +0200
> > > Olaf Hering wrote:
> > >
> > > > Since usage of g
On 04/18/2018 09:25 AM, Vladimir Sementsov-Ogievskiy wrote:
>>> Do your code with
>>>
>>> /* Found an extent, and we're inside it. */
>>> *next = f.fe.fe_logical + f.fe.fe_length;
>>> if (f.fe.fe_flags & FIEMAP_EXTENT_UNWRITTEN) {
>>> return BDRV_BLOCK_DATA|BDRV_BLOCK_ZERO;
On Wed, 18 Apr 2018 13:55:45 +0100
Daniel P. Berrangé wrote:
> On Wed, Apr 18, 2018 at 02:45:38PM +0200, Cornelia Huck wrote:
> > On Wed, 18 Apr 2018 14:38:37 +0200
> > Olaf Hering wrote:
> >
> > > Since usage of g_realloc_n was introduced, glib-2.22 can not be used
> > > anymore.
> > > Fixe
> static void s390_ipl_class_init(ObjectClass *klass, void *data)
> diff --git a/hw/s390x/ipl.h b/hw/s390x/ipl.h
> index 0570d0ad75..102f1ea7af 100644
> --- a/hw/s390x/ipl.h
> +++ b/hw/s390x/ipl.h
> @@ -87,7 +87,17 @@ int s390_ipl_set_loadparm(uint8_t *loadparm);
> void s390_ipl_update_diag308(I
On 04/18/2018 11:32 AM, Philippe Mathieu-Daudé wrote:
> Hi Marc-André,
>
> On 04/18/2018 07:36 AM, Marc-André Lureau wrote:
>> In commit cd9526ab7c04f2c32c63340b04401f6ed25682b9
>> Author: Philippe Mathieu-Daudé
>> Date: Thu Mar 8 23:39:32 2018 +0100
>>
>> hw/isa/superio: Factor out the se
Hi Marc-André,
On 04/18/2018 07:36 AM, Marc-André Lureau wrote:
> In commit cd9526ab7c04f2c32c63340b04401f6ed25682b9
> Author: Philippe Mathieu-Daudé
> Date: Thu Mar 8 23:39:32 2018 +0100
>
> hw/isa/superio: Factor out the serial code from pc87312.c
>
> You changed from:
>
> -
load_dtb() depends on arm_load_kernel() to figure out place
in RAM where it should be loaded, but it's not required for
arm_load_kernel() to work. Sometimes it's neccesary for
devices added with -device/device_add to be enumerated in
DTB as well, which's lead to [1] and surrounding commits to
add 2
On Apr 17 16:38, Aaron Lindsay wrote:
> diff --git a/target/arm/helper.c b/target/arm/helper.c
> index 046e37c..2efdc63 100644
> --- a/target/arm/helper.c
> +++ b/target/arm/helper.c
> @@ -973,6 +986,11 @@ static uint64_t cycles_get_count(CPUARMState *env)
> }
>
> #ifndef CONFIG_USER_ONLY
> +st
Convert PPCE500Params to PCCE500MachineClass which it essentially is,
and introduce PCCE500MachineState to keep track of E500 specific
state instead of adding global variables or extra parameters to
functions when we need to keep data beyond machine init
(i.e. make it look like typical fully define
if arm_load_kernel() were passed non first_cpu, QEMU would end up
with partially set do_cpu_reset() callback leaving some CPUs without it.
Make sure that do_cpu_reset() is registered for all CPUs by enumerating
CPUs from first_cpu.
Signed-off-by: Igor Mammedov
Reviewed-by: Peter Maydell
---
hw
platform-bus were using machine_done notifier to get and map
(assign irq/mmio resources) dynamically added sysbus devices
after all '-device' options had been processed.
That however creates non obvious dependencies on ordering of
machine_done notifiers and requires carefull line juggling
to keep i
By default MachineClass::get_hotplug_handler is NULL and concrete board
should set it to it's own handler.
Considering there isn't any default handler, drop saving empty
MachineClass::get_hotplug_handler in child class and make PC code
consistent with spapr/s390x boards.
We can bring this back whe
Changelog v1->v2:
* drop "arm: reuse arm_boot_address_space() in armv7m_load_kernel()"
* move "arm: always start from first_cpu when registering loader cpu reset
callback"
at the begigning of series and rebase
* add "ppc: e500: switch E500 based machines to full machine definitio
Am 18.04.2018 um 16:16 hat Eric Blake geschrieben:
> On 04/18/2018 08:50 AM, Kevin Wolf wrote:
>
> >>> @@ -3195,6 +3215,8 @@
> >>> '*conf': 'str',
> >>> '*snapshot': 'str',
> >>> '*user': 'str',
> >>> +'*auth-none': 'bool',
> >>> +'*au
15.02.2018 19:42, Paolo Bonzini wrote:
On 15/02/2018 17:40, Vladimir Sementsov-Ogievskiy wrote:
Hi all.
Two years later, is there are any news on the topic?
I can't understand the following thing:
- FIEMAP without FLAG_SYNC is unsafe
- FIEMAP with FLAG_SYNC is safe but slow
- so, we've
On 04/18/2018 08:50 AM, Kevin Wolf wrote:
>>> @@ -3195,6 +3215,8 @@
>>> '*conf': 'str',
>>> '*snapshot': 'str',
>>> '*user': 'str',
>>> +'*auth-none': 'bool',
>>> +'*auth-cephx': 'RbdAuthCephx',
>>> '*server': ['InetSocket
On 18.04.2018 16:08, Thomas Huth wrote:
> On 12.04.2018 21:26, David Hildenbrand wrote:
>> Calling pause_all_vcpus()/resume_all_vcpus() from a VCPU thread might
>> not be the best idea. As pause_all_vcpus() temporarily drops the qemu
>> mutex, two parallel calls to pause_all_vcpus() can be active a
On 12.04.2018 21:26, David Hildenbrand wrote:
> Calling pause_all_vcpus()/resume_all_vcpus() from a VCPU thread might
> not be the best idea. As pause_all_vcpus() temporarily drops the qemu
> mutex, two parallel calls to pause_all_vcpus() can be active at a time,
> resulting in a deadlock. (either
On 04/13/2018 01:14 PM, Vladimir Sementsov-Ogievskiy wrote:
> Handle new NBD meta namespace: "qemu", and corresponding queries:
> "qemu:dirty-bitmap:".
>
> With new metadata context negotiated, BLOCK_STATUS query will reply
> with dirty-bitmap data, converted to extents. New public function
> nbd_
On Wed, Apr 18, 2018 at 04:03:03PM +0200, Laszlo Ersek wrote:
> On 04/18/18 15:53, Daniel P. Berrangé wrote:
> > On Wed, Apr 18, 2018 at 03:30:36PM +0200, Laszlo Ersek wrote:
> >> On 04/18/18 15:06, Gerd Hoffmann wrote:
> > Other question: Do we want allow to specify which certs/keys are
> >>>
1 - 100 of 202 matches
Mail list logo
