From: Greg Kurz
Some PHB implementations, eg. PAPR used on pseries machine, act like
a regular PCI bus rather than a PCIe bus, but allow access to the
PCIe extended config space anyway.
Introduce a new PCI bus class method to modelize this behaviour and
use it when adjusting the config space siz
The following changes since commit 5263724b78f89cdea2354c8e92c53bac1b4641a3:
Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into staging
(2019-04-08 17:53:18 +0100)
are available in the Git repository at:
git://github.com/dgibson/qemu.git tags/ppc-for-4.0-2019040
From: Greg Kurz
The PAPR PHB acts as a legacy PCI bus but it allows PCIe extended
config space accesses anyway (for pseries-2.9 and newer machine
types).
Introduce a specific PCI bus subtype to inform the common PCI code
about that.
Fixes: c2077e2ca0da7
Signed-off-by: Greg Kurz
Message-Id: <15
Thomas Huth writes:
> We'd like to get rid of global_qtest in the long run (since it is
> causing trouble for tests that run multiple instances of QEMU in
> parallel, e.g. migration tests)... so if it is feasible, please don't
> use it in new code anymore. Try to use a local variable in the funct
On 09/04/2019 09.45, Markus Armbruster wrote:
> Thomas Huth writes:
>
>> We'd like to get rid of global_qtest in the long run (since it is
>> causing trouble for tests that run multiple instances of QEMU in
>> parallel, e.g. migration tests)... so if it is feasible, please don't
>> use it in new
Am 09.04.2019 um 08:01 hat Markus Armbruster geschrieben:
> László's last sentence below is "This really needs the attention of the
> block people." Cc'ing some.
>
> Laszlo Ersek writes:
>
> > On 04/08/19 15:43, Xiang Zheng wrote:
> >>
> >> On 2019/4/3 23:35, Laszlo Ersek wrote:
> I thoug
Thomas Huth writes:
> On 09/04/2019 09.45, Markus Armbruster wrote:
>> Thomas Huth writes:
>>
>>> We'd like to get rid of global_qtest in the long run (since it is
>>> causing trouble for tests that run multiple instances of QEMU in
>>> parallel, e.g. migration tests)... so if it is feasible, p
On 09/04/2019 10.35, Markus Armbruster wrote:
> Thomas Huth writes:
>
>> On 09/04/2019 09.45, Markus Armbruster wrote:
>>> Thomas Huth writes:
>>>
We'd like to get rid of global_qtest in the long run (since it is
causing trouble for tests that run multiple instances of QEMU in
par
Thomas Huth writes:
> On 09/04/2019 10.35, Markus Armbruster wrote:
>> Thomas Huth writes:
>>
>>> On 09/04/2019 09.45, Markus Armbruster wrote:
Thomas Huth writes:
> We'd like to get rid of global_qtest in the long run (since it is
> causing trouble for tests that run multipl
While global_qtest and its wrapper functions work fine for tests that only
run one instance of QEMU, using the global_qtest variable in our qtests is
very problematic for tests that use multiple test states (e.g. migration
tests). Thus tests that still use global_qtest make it hard to share code
(e
Pass around the QTestState in the TestData, so we do not need the
global_qtest variable here anymore.
Signed-off-by: Thomas Huth
---
tests/tco-test.c | 63
1 file changed, 32 insertions(+), 31 deletions(-)
diff --git a/tests/tco-test.c b/tests/tc
qtest_start() + qtest_end() should be avoided, since they use the
global_qtest variable that we want to get rid of in the long run
(since global_qtest can not be used in tests that have to track
multiple QEMU states, like migration tests). Use qtest_init() and
qtest_quit() instead.
Signed-off-by:
qtest_start() + qtest_end() should be avoided, since they use the
global_qtest variable that we want to get rid of in the long run
Use qtest_init() and qtest_quit() instead.
Signed-off-by: Thomas Huth
---
tests/test-hmp.c | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
The test uses memwrite() and thus relies on global_qtest. Let's replace it
with qtest_memwrite(), so that we are independent from global_qtest here.
Signed-off-by: Thomas Huth
---
tests/megasas-test.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/megasas-test.c b/test
Pass around the QTestState, so we do not need the problematic global_qtest
variable (which causes trouble for tests that have multiple test states)
here anymore.
Signed-off-by: Thomas Huth
---
tests/ide-test.c | 284 ++-
1 file changed, 159 insertions(
08.04.2019 21:22, Andrey Shinkevich wrote:
> This patch is used in the 'block/stream: introduce a bottom node'
> that is following. Instead of the base node, the caller may pass
> the node that has the base as its backing image to the function
> bdrv_is_allocated_above() with a new parameter includ
08.04.2019 21:22, Andrey Shinkevich wrote:
> The bottom node is the intermediate block device that has the base as its
> backing image. It is used instead of the base node while a block stream
> job is running to avoid dependency on the base that may change due to the
> parallel jobs. The change ma
>
> Lidong Chen writes:
>
> > Due to an off-by-one error, the assert statements allow an
> > out-of-bounds array access.
> >
> > Signed-off-by: Lidong Chen
> > ---
> > hw/sd/sd.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/hw/sd/sd.c b/hw/sd/sd.c
> > index
* Ilya Maximets (i.maxim...@samsung.com) wrote:
> > Hi everyone,
> >
> >
> >
> > The following new patches are queued for QEMU stable v3.0.1:
> >
> > https://github.com/mdroth/qemu/commits/stable-3.0
On Mon, 8 Apr 2019 at 20:04, Eric Blake wrote:
>
> The following changes since commit 2c573106279495795449b0d0373464b597dfe316:
>
> Merge remote-tracking branch
> 'remotes/huth-gitlab/tags/pull-request-2019-04-08' into staging (2019-04-08
> 15:21:11 +0100)
>
> are available in the Git reposito
* Thomas Huth (th...@redhat.com) wrote:
> qtest_start() + qtest_end() should be avoided, since they use the
> global_qtest variable that we want to get rid of in the long run
> Use qtest_init() and qtest_quit() instead.
>
> Signed-off-by: Thomas Huth
Reviewed-by: Dr. David Alan Gilbert
> ---
>
On 4/7/19 3:05 PM, Sukrit Bhatnagar wrote:
Hi,
Are the patches in good enough shape to be merged?
Hi Sukrit,
Where is the patch itself :) ?
Also be sure to add the maintainers to cc.
You can get them by running ./scripts/get_maintainers.pl script on your
patch.
Please re-send it.
Thank
On 18/03/2019 18.15, Paolo Bonzini wrote:
> Currently, if qos_node_contains was passed options, it would still
> create an edge without any options. Instead, in that case
> NULL acts as a terminator.
>
> Signed-off-by: Paolo Bonzini
> ---
> tests/libqos/qgraph.c | 12
> tests/libqo
On 4/9/19 10:59 AM, Aleksandar Markovic wrote:
>>
>> Lidong Chen writes:
>>
>>> Due to an off-by-one error, the assert statements allow an
>>> out-of-bounds array access.
>>>
>>> Signed-off-by: Lidong Chen
>>> ---
>>> hw/sd/sd.c | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>
Markus wrote:
> This is the second fix for this bug pattern in a fortnight. Where's
> one, there are more:
>
> $ git-grep '<= ARRAY_SIZE'
> hw/intc/arm_gicv3_cpuif.c:assert(aprmax <= ARRAY_SIZE(cs->ich_apr[0]));
> hw/intc/arm_gicv3_cpuif.c:assert(aprmax <= ARRAY_SIZE(cs->ich_apr[0]));
>
On 18/03/2019 18.15, Paolo Bonzini wrote:
> The functions to read/write 8-bit or 16-bit registers are the same
> in tmp105 and pca9552 tests, and in fact they are a special case of
> "read block"/"write block" functionality; read block in turn is used
> in ds1338-test.
>
> Move everything inside l
On Tue, 9 Apr 2019 07:33:20 +0200
Stefan Weil wrote:
> The last *.aml file was removed in commit
> 13b1881aacc7e5018773bd545bbaf8d5476699ee.
>
> Signed-off-by: Stefan Weil
Reviewed-by: Igor Mammedov
> ---
> configure | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/configure b/con
On Tue, 9 Apr 2019 at 06:51, Markus Armbruster wrote:
> $ git-grep '<= ARRAY_SIZE'
Almost all of these are OK because they're the pattern of
checking a loop upper bound before doing a loop.
> hw/intc/arm_gicv3_cpuif.c:assert(aprmax <= ARRAY_SIZE(cs->ich_apr[0]));
> hw/intc/arm_gicv3_cpuif.c:
On 18/03/2019 18.15, Paolo Bonzini wrote:
> receive_autoinc is relying on the LED state that is set by
> send_and_receive. Stop doing that, because qgraph resets the
> machine between tests.
>
> Signed-off-by: Paolo Bonzini
> ---
> tests/pca9552-test.c | 15 +++
> 1 file changed, 11
On 18/03/2019 18.15, Paolo Bonzini wrote:
> There is no need to have a test device created by the board.
> Instead, create it in the qtest so that we will be able to run
> it on other boards too.
>
> Signed-off-by: Paolo Bonzini
> ---
> hw/arm/imx25_pdk.c | 9 -
> tests/ds1338-test.c |
Am 02.04.2019 um 10:35 hat Denis Plotnikov geschrieben:
>
>
> On 13.03.2019 19:04, Kevin Wolf wrote:
> > Am 14.12.2018 um 12:54 hat Denis Plotnikov geschrieben:
> >> On 13.12.2018 15:20, Kevin Wolf wrote:
> >>> Am 13.12.2018 um 12:07 hat Denis Plotnikov geschrieben:
> Sounds it should be so,
This is in preparation for adding support for ARM64 platforms
where it doesn't use port mapped IO for ACPI IO space.
Also move few MEMORY_* definitions to header so that other memory
hotplug event signalling mechanisms (eg. Generic Event Device on
HW-reduced acpi platforms) can use the same from t
This series is an attempt to provide device memory hotplug support
on ARM virt platform. This is based on Eric's recent works here[1]
and carries some of the pc-dimm related patches dropped from his
series.
The kernel support for arm64 memory hot add was added recently by
Robin and hence the gues
From: Samuel Ortiz
With Hardware-reduced ACPI, the GED device will manage ACPI
hotplug entirely. As a consequence, make the memory specific
events AML generation optional. The code will only be added
when the method name is not NULL.
Signed-off-by: Samuel Ortiz
Signed-off-by: Shameer Kolothum
From: Samuel Ortiz
The ACPI Generic Event Device (GED) is a hardware-reduced specific
device[ACPI v6.1 Section 5.6.9] that handles all platform events,
including the hotplug ones.This patch generates the AML code that
defines GEDs.
Platforms need to specify their own GedEvent array to describe w
Currently firmware has no way of differentiating the memory
nodes and as a result device memory nodes might get exposed
to Guest Kernel via UEFI GetMemoryMap() as early boot memory
even if Guest boots with ACPI. This will prevent hot-unplug
of the device memory. To address this, an additional
"hotp
Hi Stephen,
[Cc'ing Markus and Laszlo, we have similar interest in pflash01 testing]
On 4/8/19 10:55 PM, Stephen Checkoway wrote:
> The goal of this patch series implement the following AMD command-set parallel
> flash functionality:
> - flash interleaving;
> - nonuniform sector sizes;
> - erase
From: Eric Auger
This patch adds the memory hot-plug/hot-unplug infrastructure
in machvirt. The device memory is not yet exposed to the Guest
either though DT or ACPI and hence both cold/hot plug of memory
is explicitly disabled for now.
Signed-off-by: Eric Auger
Signed-off-by: Kwangwoo Lee
Si
Generate Memory Affinity Structures for PC-DIMM ranges.
Signed-off-by: Shameer Kolothum
Signed-off-by: Eric Auger
Reviewed-by: Igor Mammedov
---
hw/arm/virt-acpi-build.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/hw/arm/virt-acpi-build.c b/hw/arm/virt-acpi-build.c
index 1ad39
On 4/9/19 7:33 AM, Stefan Weil wrote:
> The last *.aml file was removed in commit
> 13b1881aacc7e5018773bd545bbaf8d5476699ee.
>
> Signed-off-by: Stefan Weil
Reviewed-by: Philippe Mathieu-Daudé
> ---
> configure | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/configure b/configure
>
This initializes the GED device with base memory and irq, configures
ged memory hotplug event and builds the corresponding aml code. GED
irq routing to Guest is also enabled. With this, both hot and cold
plug of device memory is enabled now for Guest with ACPI boot.
Memory cold plug support with G
This patch adds memory nodes corresponding to PC-DIMM regions.
This will enable support for cold plugged device memory for Guests
with DT boot.
Signed-off-by: Shameer Kolothum
Signed-off-by: Eric Auger
---
hw/arm/boot.c | 42 ++
1 file changed, 42 inserti
On 4/8/19 2:31 PM, Markus Armbruster wrote:
> Marc-André Lureau writes:
>
>> Hi
>>
>> On Mon, Apr 8, 2019 at 10:36 AM Markus Armbruster wrote:
>>>
>>> char_pty_open() prints a "char device redirected to PTY_NAME (label
>>> LABEL)" message to the current monitor or else to stderr. No other
>>> C
On 09/04/2019 06:51, Markus Armbruster wrote:
Lidong Chen writes:
Due to an off-by-one error, the assert statements allow an
out-of-bounds array access.
Signed-off-by: Lidong Chen
Reviewed-by: Liam Merwick
---
hw/sd/sd.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
di
> -Original Message-
> From: Igor Mammedov [mailto:imamm...@redhat.com]
> Sent: 08 April 2019 09:12
> To: Shameerali Kolothum Thodi
> Cc: Laszlo Ersek ; Auger Eric ;
> Ard Biesheuvel ; peter.mayd...@linaro.org;
> sa...@linux.intel.com; qemu-devel@nongnu.org; Linuxarm
> ; shannon.zha...@
Fix the check preventing calling pixman functions that would access
memory outside allocated vram. The r128 X driver sometimes seem to try
blits that span outside vram, this check prevents crashing QEMU in
that case. (The r128 X driver may have problems even on real hardware
so I'm not sure if it's
On Sat, Apr 06, 2019 at 09:34:22AM +0530, Aruna Jayasena wrote:
> Removed unwanted includes from cpu-common.h
> This task was under https://wiki.qemu.org/Contribute/BiteSizedTasks
>
> Signed-off-by: Aruna Jayasena
> ---
> include/exec/cpu-common.h | 2 --
> 1 file changed, 2 deletions(-)
Hi Aru
Hi
On Tue, Apr 9, 2019 at 12:40 PM Philippe Mathieu-Daudé
wrote:
>
> On 4/8/19 2:31 PM, Markus Armbruster wrote:
> > Marc-André Lureau writes:
> >
> >> Hi
> >>
> >> On Mon, Apr 8, 2019 at 10:36 AM Markus Armbruster
> >> wrote:
> >>>
> >>> char_pty_open() prints a "char device redirected to PTY
On Tue, Apr 02, 2019 at 02:19:08PM +0200, Sergio Lopez wrote:
> The polling mode in aio_poll is able to trim down ~20us on the average
> request latency, but it needs manual fine tuning to adjust it to the
> characteristics of the storage.
>
> Here we add a new knob to the IOThread object, "poll-i
On 4/8/19 9:30 PM, John Snow wrote:
> On 4/8/19 1:38 AM, Markus Armbruster wrote:
>> Hervé Poussineau writes:
>>
>>> Le 05/04/2019 à 12:29, Philippe Mathieu-Daudé a écrit :
Hi,
I am trying to understand the possible values for the MAX_FD variable
used by the floppy controller m
On Mon, 8 Apr 2019 at 20:38, Laurent Vivier wrote:
>
> The following changes since commit f55a585d1037e5de6088f25e75443c2776786e29:
>
> Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging
> (2019-04-07 14:54:55 +0100)
>
> are available in the Git repository at:
>
> git:/
On Mon, 18 Mar 2019 at 17:07, Paolo Bonzini wrote:
>
> On 18/03/19 12:29, Peter Maydell wrote:
> > In the accessor functions ld*_he_p() and st*_he_p() we use memcpy()
> > to perform a load or store to a pointer which might not be aligned
> > for the size of the type. We rely on the compiler to opt
he Git repository at:
>
> git://github.com/dgibson/qemu.git tags/ppc-for-4.0-20190409
>
> for you to fetch changes up to 5cf0d326a0fec9ebac2d47c42b5f08e6bc2f686c:
>
> spapr_pci: Fix extended config space accesses (2019-04-09 15:03:10 +1000)
>
> ---
With aio=thread, adaptive polling makes latency worse rather than
better, because it delays the execution of the ThreadPool's
completion bottom half.
event_notifier_poll() does run while polling, detecting that
a bottom half was scheduled by a worker thread, but because
ctx->notifier is explicitly
On Tue, 26 Mar 2019 at 12:26, Peter Maydell wrote:
>
> On Mon, 25 Mar 2019 at 18:13, Juan Quintela wrote:
> >
> > This way we can change the packet size in the future and everything
> > will work. We choose an arbitrary big number (100 times configured
> > size) as a limit about how big we will
This patch looks 4.0 worthwhile.
On 4/9/19 12:56 PM, BALATON Zoltan wrote:
> Fix the check preventing calling pixman functions that would access
> memory outside allocated vram. The r128 X driver sometimes seem to try
> blits that span outside vram, this check prevents crashing QEMU in
> that case
On Mon 08 Apr 2019 08:17:37 PM CEST, Andrey Shinkevich wrote:
>>> +for (iter = bs; iter != bottom; iter = backing_bs(iter)) {
>>> +block_job_add_bdrv(&s->common, "intermediate node",
>>> backing_bs(iter),
>>> + 0, basic_flags, &error_abort);
>>> }
>>
>>
On Thu, 28 Mar 2019 at 11:14, Paolo Bonzini wrote:
>
> On 28/03/19 11:47, Peter Maydell wrote:
> > Fix a TCG crash due to attempting an atomic increment
> > operation without having set up the address first.
> > This is a similar case to that dealt with in commit
> > e84fcd7f662a0d8198703, and we
On Mon 08 Apr 2019 08:22:21 PM CEST, Andrey Shinkevich wrote:
> The bottom node is the intermediate block device that has the base as its
> backing image. It is used instead of the base node while a block stream
> job is running to avoid dependency on the base that may change due to the
> parallel
On Mon, Apr 01, 2019 at 02:18:43PM +0300, Yoni Bettan wrote:
> The main goal is to add an example device to Qemu to be used as template or
> guideline for contributors when they wish to create a new virtio device.
>
> Another reason for this device is to document "the right way" to write
> a new v
On 08/04/2019 22:03, Max Reitz wrote:
> On 28.02.19 10:26, Andrey Shinkevich wrote:
>> When a bitmap is removed, we can clean some space on the disk. The size
>> of a cluster may be larger, so is the size of the bitmap that includes
>> many clusters. Some bitmaps can be as large as tens of megaby
On Fri, Apr 05, 2019 at 03:41:17PM -0600, Kenneth Heitke wrote:
> Signed-off-by: Kenneth Heitke
> ---
> hw/block/nvme.c | 120 +-
> hw/block/nvme.h | 3 ++
> hw/block/trace-events | 2 +
> include/block/nvme.h | 2 +
> 4 files changed, 12
** Tags added: linux-user
** Tags added: arm
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1823790
Title:
QEMU forces systemd into tight loop
Status in QEMU:
New
Bug description:
While build
The patch from comment #3 is now in git master and will be in the 4.0
release.
** Changed in: qemu
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1807675
As described on the systemd issue, the syscall we're getting wrong here
is getsockopt(fd, SOL_SOCKET, SO_PEERSEC, ...). Our linux-
user/syscall.c:do_getsockopt() doesn't have any special case code for
the payload on this function, so we treat it as if it were just an
integer payload, which is not c
Hi,
Two trivial fixes to avoid the latest EDK2 testing series to
cause trouble to downstream distributions (in particular if
they have PIE enforced).
Since v2:
- addressed Laszlo's suggestion
- reworded patch description
v2: https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg01033.html
v1:
The iPXE's 'veryclean' recipe removes $(EFIROM) even if the EFIROM
macro originates from elsewhere:
$ git checkout f590a812c21~
$ make -C roms clean EFIROM=$(type -P EfiRom)
make: Entering directory '/source/qemu/roms'
[...]
make -C ipxe/src veryclean
make[1]: Entering directory '/sour
** Tags removed: usermode
** Tags added: linux-user
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1812861
Title:
QEMU in user-mode emulation mode crashes when the user program jumps
to an invalid
Since commit f590a812c210 we build the EDK2 EfiRom utility
unconditionally.
Some distributions require to use extra compiler/linker flags,
i.e. SUSE which enforces the PIE protection (see [*]).
EDK2 build tools already provide a set of variables for that,
use them to allow the caller to easily in
On Tue, 9 Apr 2019 at 14:47, Philippe Mathieu-Daudé wrote:
>
> Hi,
>
> Two trivial fixes to avoid the latest EDK2 testing series to
> cause trouble to downstream distributions (in particular if
> they have PIE enforced).
>
> Since v2:
> - addressed Laszlo's suggestion
> - reworded patch descriptio
Your suggested fix looks good -- did you want to send it to qemu-devel
with a suitable Signed-off-by: line ?
** Tags added: linux-user
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QE
Hi
On Thu, Apr 12, 2018 at 4:49 PM Dr. David Alan Gilbert
wrote:
>
> * Marc-André Lureau (marcandre.lur...@redhat.com) wrote:
> > Make screendump asynchronous to provide correct screendumps.
> >
> > HMP doesn't have async support, so it has to remain synchronous and
> > potentially incorrect to a
From: Zhuang Yanying
Recently I tested the performance of NVMe SSD passthrough and found that
interrupts
were aggregated on vcpu0(or the first vcpu of each numa) by
/proc/interrupts,when
GuestOS was upgraded to sles12sp3 (or redhat7.6). But
/proc/irq/X/smp_affinity_list
shows that the interrup
On Mon 08 Apr 2019 08:22:19 PM CEST, Andrey Shinkevich wrote:
> * Return true if (a prefix of) the given range is allocated in any image
> - * between BASE and TOP (inclusive). BASE can be NULL to check if the given
> + * between BASE and TOP (TOP included). To check the BASE image, set the
> +
On Thu, Mar 21, 2019 at 09:55:42AM +0200, Nir Weiner wrote:
> Originally migration was not possible with vhost-scsi because
> as part of migration, the source host target SCSI device state
> needs to be saved and loaded into the destination host target SCSI
> device. This cannot be done by QEMU.
>
09.04.2019 17:18, Alberto Garcia wrote:
> On Mon 08 Apr 2019 08:22:19 PM CEST, Andrey Shinkevich wrote:
>>* Return true if (a prefix of) the given range is allocated in any image
>> - * between BASE and TOP (inclusive). BASE can be NULL to check if the given
>> + * between BASE and TOP (TOP in
On Tue 09 Apr 2019 04:43:12 PM CEST, Vladimir Sementsov-Ogievskiy wrote:
>>> -while (intermediate && intermediate != base) {
>>> +while (include_base || intermediate != base) {
>>> int64_t pnum_inter;
>>> int64_t size_inter;
>>>
>>> @@ -2360,6 +2364,10 @@ int bdrv_is_
On Tue, Apr 09, 2019 at 02:14:56PM +, Zhuangyanying wrote:
> From: Zhuang Yanying
>
> Recently I tested the performance of NVMe SSD passthrough and found that
> interrupts
> were aggregated on vcpu0(or the first vcpu of each numa) by
> /proc/interrupts,when
> GuestOS was upgraded to sles12s
On Fri, 5 Apr 2019 16:55:30 +0800
Wei Yang wrote:
> On Tue, Apr 02, 2019 at 08:15:12AM +0200, Igor Mammedov wrote:
> >On Tue, 2 Apr 2019 11:53:43 +0800
> >Wei Yang wrote:
> >
> >
> >> The migration infrastructure has several SaveStateEntry to help migrate
> >> different elements. The one with
The 'qemu-img convert' new command option 'force read' with the key '-R'
allows converting a damaged image to get all the available information
in case of the read errors. The program reports read errors and continue
the image conversion. The users should keep in their minds that the
resulting imag
The 'qemu-img convert' new command option 'force read' with the key '-R'
allows converting a damaged image to get all the available information
in case of the read errors. The program reports read errors and continue
the image conversion. The users should keep in their minds that the
resulting imag
A new test for the patch 'qemu-img convert: ignore read errors'
Signed-off-by: Andrey Shinkevich
---
tests/qemu-iotests/253 | 69 ++
tests/qemu-iotests/253.out | 4 +++
tests/qemu-iotests/group | 1 +
3 files changed, 74 insertions(+)
create m
On Tue, 9 Apr 2019 15:45:36 +0200
Philippe Mathieu-Daudé wrote:
> Since commit f590a812c210 we build the EDK2 EfiRom utility
> unconditionally.
>
> Some distributions require to use extra compiler/linker flags,
> i.e. SUSE which enforces the PIE protection (see [*]).
>
> EDK2 build tools alrea
Dummy table (with signature "QEMU") creation came from original SeaBIOS
codebase. And QEMU would have to keep it around if there were Q35 machine
that depended on keeping ACPI tables blob constant size. Luckily there
were no versioned Q35 machine types before commit:
(since 2.3) a1666142db acpi-b
On Tue, Apr 09, 2019 at 02:14:56PM +, Zhuangyanying wrote:
> From: Zhuang Yanying
>
> Recently I tested the performance of NVMe SSD passthrough and found that
> interrupts
> were aggregated on vcpu0(or the first vcpu of each numa) by
> /proc/interrupts,when
> GuestOS was upgraded to sles12s
On Tue, Apr 09, 2019 at 03:45:34PM +0200, Philippe Mathieu-Daudé wrote:
> Hi,
>
> Two trivial fixes to avoid the latest EDK2 testing series to
> cause trouble to downstream distributions (in particular if
> they have PIE enforced).
>
> Since v2:
> - addressed Laszlo's suggestion
> - reworded patc
On 04/09/19 12:29, Shameer Kolothum wrote:
> This patch adds memory nodes corresponding to PC-DIMM regions.
> This will enable support for cold plugged device memory for Guests
> with DT boot.
>
> Signed-off-by: Shameer Kolothum
> Signed-off-by: Eric Auger
> ---
> hw/arm/boot.c | 42 +++
On Tue, 9 Apr 2019 at 16:06, Michael S. Tsirkin wrote:
>
> On Tue, Apr 09, 2019 at 03:45:34PM +0200, Philippe Mathieu-Daudé wrote:
> > Hi,
> >
> > Two trivial fixes to avoid the latest EDK2 testing series to
> > cause trouble to downstream distributions (in particular if
> > they have PIE enforced
Coverity points out (CID 1400442) that in this code:
if (packet->pages_alloc > p->pages->allocated) {
multifd_pages_clear(p->pages);
multifd_pages_init(packet->pages_alloc);
}
we free p->pages in multifd_pages_clear() but continue to
use it in the following code. We also l
On 04/09/19 15:45, Philippe Mathieu-Daudé wrote:
> The iPXE's 'veryclean' recipe removes $(EFIROM) even if the EFIROM
> macro originates from elsewhere:
>
> $ git checkout f590a812c21~
> $ make -C roms clean EFIROM=$(type -P EfiRom)
> make: Entering directory '/source/qemu/roms'
> [...]
>
On 04/09/19 15:45, Philippe Mathieu-Daudé wrote:
> Since commit f590a812c210 we build the EDK2 EfiRom utility
> unconditionally.
>
> Some distributions require to use extra compiler/linker flags,
> i.e. SUSE which enforces the PIE protection (see [*]).
>
> EDK2 build tools already provide a set o
On 04/09/19 16:00, Peter Maydell wrote:
> On Tue, 9 Apr 2019 at 14:47, Philippe Mathieu-Daudé wrote:
>>
>> Hi,
>>
>> Two trivial fixes to avoid the latest EDK2 testing series to
>> cause trouble to downstream distributions (in particular if
>> they have PIE enforced).
>>
>> Since v2:
>> - addresse
On Tue, 9 Apr 2019 at 16:25, Laszlo Ersek wrote:
>
> On 04/09/19 16:00, Peter Maydell wrote:
> > Thanks. This is one of a handful of remaining bugs we
> > should fix for 4.0, so I would ideally like to get this
> > in rc3 today (or tomorrow if we have to slip rc3 a day).
> > If people wanting to r
On Apr 9, 2019, at 02:13, Thomas Huth wrote:
> We'd like to get rid of global_qtest in the long run (since it is
> causing trouble for tests that run multiple instances of QEMU in
> parallel, e.g. migration tests)... so if it is feasible, please don't
> use it in new code anymore. Try to use a
min-glib.docker was removed in commit
e7b3af81597db1a6b55f2c15d030d703c6b2c6ac ("glib: bump min required
glib library version to 2.40").
Cc: Daniel P. Berrangé
Signed-off-by: Marc-André Lureau
---
docs/devel/testing.rst | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a
Peter Maydell wrote:
> Coverity points out (CID 1400442) that in this code:
>
> if (packet->pages_alloc > p->pages->allocated) {
> multifd_pages_clear(p->pages);
> multifd_pages_init(packet->pages_alloc);
> }
>
> we free p->pages in multifd_pages_clear() but continue to
> u
From: Thomas Huth
QEMU currently crashes when you try to hot-plug an "nvdimm" device
on older machine types:
$ qemu-system-x86_64 -monitor stdio -M pc-1.1
QEMU 3.1.92 monitor - type 'help' for more information
(qemu) device_add nvdimm,id=nvdimmn1
qemu-system-x86_64: /home/thuth/devel/qemu/util/e
From: Philippe Mathieu-Daudé
Since commit f590a812c210 we build the EDK2 EfiRom utility
unconditionally.
Some distributions require to use extra compiler/linker flags,
i.e. SUSE which enforces the PIE protection (see [*]).
EDK2 build tools already provide a set of variables for that,
use them t
From: Markus Armbruster
Fixes: b93b63f574c "test makefile overhaul"
Signed-off-by: Markus Armbruster
Reviewed-by: Eric Blake
Message-Id: <20190319072104.32591-1-arm...@redhat.com>
Signed-off-by: Paolo Bonzini
---
tests/Makefile.include | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
d
Removed unwanted includes from cpu-common.h
This task was under https://wiki.qemu.org/Contribute/BiteSizedTasks
Signed-off-by: Aruna Jayasena
---
include/exec/cpu-common.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/exec/cpu-common.h b/include/exec/cpu-common.h
index cef8b88a2a
1 - 100 of 235 matches
Mail list logo
