This makes the powernv machine easier for end users as the default
initrd address is now within RAM.
Signed-off-by: Joel Stanley
--
This replaces https://patchwork.ozlabs.org/patch/1132438/
hw/ppc/pnv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/ppc/pnv.c
Hi Michael,
On 7/17/19 5:46 PM, Michael Rolnik wrote:
> ping.
QEMU is currently preparing for the next release (4.1) and we entered
the "freezed" period where no new features are accepted.
This does not mean people are not allowed to post new features to the
list, but most volunteering
On Tue, 16 Jul 2019 at 08:53, David Gibson wrote:
>
> On Tue, Jul 16, 2019 at 09:39:36AM +0200, Cédric Le Goater wrote:
> > > Provide a helpful message for users so they don't go reporting bugs to
> > > kernel developers.
> > >
> > > Signed-off-by: Joel Stanley
> > > ---
> > > We could solve
On 7/17/19 11:47 AM, Paolo Bonzini wrote:
> The argument is not used and passing it clutters error propagation in the
> callers. So, get rid of it.
>
> Signed-off-by: Paolo Bonzini
> ---
> hw/scsi/vhost-scsi.c| 2 +-
> hw/scsi/vhost-user-scsi.c | 2 +-
> hw/scsi/virtio-scsi.c
Cc'ing qemu-block@
On 7/18/19 5:25 AM, no-re...@patchew.org wrote:
> Patchew URL:
> https://patchew.org/QEMU/20190717094728.31006-1-pbonz...@redhat.com/
[...]> time make docker-test-debug@fedora TARGET_LIST=x86_64-softmmu
J=14 NETWORK=1
[...]
> PASS 18 test-bdrv-drain
On 7/11/2019 1:38 PM, Jing Liu wrote:
Intel CooperLake cpu adds AVX512_BF16 instruction, defining as
CPUID.(EAX=7,ECX=1):EAX[bit 05].
The release spec link as follows,
https://software.intel.com/sites/default/files/managed/c5/15/\
On Wed, Jul 17, 2019 at 03:53:47PM -0500, Michael Roth wrote:
> Quoting David Gibson (2019-07-16 20:29:12)
> > On Tue, Jul 16, 2019 at 11:30:01AM -0500, Michael Roth wrote:
> > > Quoting David Gibson (2019-07-14 21:25:24)
> > > > On Fri, Jul 12, 2019 at 09:34:46AM -0500, Michael Roth wrote:
> > >
This has been useful to modify and test the Linux pseries suspend
code but it requires modification to the guest to call it (due to
being gated by other unimplemented features). It is not otherwise
used by Linux yet, but work is slowly progressing there.
Signed-off-by: Nicholas Piggin
---
This does not do directed yielding and is not quite as strict as PAPR
specifies in terms of precise dispatch behaviour. This generally will
mean suboptimal performance, rather than guest misbehaviour. Linux
does not rely on exact dispatch behaviour.
Signed-off-by: Nicholas Piggin
---
Changes
H_PROD is added, and H_CEDE is modified to test the prod bit
according to PAPR.
Signed-off-by: Nicholas Piggin
---
Changes since v5:
- Add the prod bit here
- Fix target CPU
hw/ppc/spapr.c | 1 +
hw/ppc/spapr_hcall.c| 32
Implement cpu_exec_enter/exit on ppc which calls into new methods of
the same name in PPCVirtualHypervisorClass. These are used by spapr
to implement the splpar VPA dispatch counter initially.
Signed-off-by: Nicholas Piggin
---
Changes since v5:
- Move 'prod' into next patch.
- Use uint32_t type
Lot of good reviews (thanks), several more bug fixes and some good
cleanups.
Thanks,
Nick
Nicholas Piggin (4):
spapr: Implement dispatch tracking for tcg
spapr: Implement H_PROD
spapr: Implement H_CONFER
spapr: Implement H_JOIN
hw/ppc/spapr.c | 54
Patchew URL:
https://patchew.org/QEMU/20190717094728.31006-1-pbonz...@redhat.com/
Hi,
This series failed the asan build test. Please find the testing commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
Greg Kurz's on July 18, 2019 3:30 am:
> On Wed, 17 Jul 2019 15:39:52 +1000
> Nicholas Piggin wrote:
>
>> This has been useful to modify and test the Linux pseries suspend
>> code but it requires modification to the guest to call it (due to
>> being gated by other unimplemented features). It is
Cédric Le Goater's on July 17, 2019 11:33 pm:
> On 17/07/2019 07:39, Nicholas Piggin wrote:
>> H_PROD is added, and H_CEDE is modified to test the prod bit
>> according to PAPR.
>>
>> Signed-off-by: Nicholas Piggin
>> ---
>> hw/ppc/spapr_hcall.c | 29 +
>> 1 file
Greg Kurz's on July 18, 2019 3:00 am:
> On Wed, 17 Jul 2019 15:39:51 +1000
> Nicholas Piggin wrote:
>
>> This does not do directed yielding and is not quite as strict as PAPR
>> specifies in terms of precise dispatch behaviour. This generally will
>> mean suboptimal performance, rather than
Greg Kurz's on July 18, 2019 1:29 am:
> On Wed, 17 Jul 2019 15:39:49 +1000
> Nicholas Piggin wrote:
>
>> -cpu->machine_data = g_new0(SpaprCpuState, 1);
>> +spapr_cpu = g_new0(SpaprCpuState, 1);
>> +cpu->machine_data = spapr_cpu;
>
> What's the purpose of this change since there's no
Cédric Le Goater's on July 17, 2019 10:50 pm:
> On 17/07/2019 07:39, Nicholas Piggin wrote:
>> Implement cpu_exec_enter/exit on ppc which calls into new methods of
>> the same name in PPCVirtualHypervisorClass. These are used by spapr
>> to implement these splpar elements, used in subsequent
On 7/18/2019 2:38 AM, Eduardo Habkost wrote:
On Wed, Jul 17, 2019 at 01:39:01PM +0800, Tao Xu wrote:
Hi Eduardo,
Could I ask a question about introducing a old CPU model? Maybe not so old
because it was launched in 2017. It is the former generation (Atom Server)
of Snowridge and if this cpu
On Thu, Jul 18, 2019 at 09:04:54AM +0800, Wei Yang wrote:
> Patch 1 refine bitmap_set a little.
> Patch 2 add related test case to bitmap_set.
>
> v3:
> * free bmap
> * all 1's set correctly
> * expand range to 2 long
> * check each possible of offset
> * add a skeleton to test both
On Thu, Jul 18, 2019 at 09:25:47AM +0800, Wei Yang wrote:
> RAMBlock->used_length is always passed to migration_bitmap_sync_range(),
> which could be retrieved from RAMBlock.
>
> Suggested-by: Paolo Bonzini
> Signed-off-by: Wei Yang
Reviewed-by: Peter Xu
--
Peter Xu
RAMBlock->used_length is always passed to migration_bitmap_sync_range(),
which could be retrieved from RAMBlock.
Suggested-by: Paolo Bonzini
Signed-off-by: Wei Yang
---
migration/ram.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/migration/ram.c
On Wed, Jul 17, 2019 at 11:17:50AM +0200, Paolo Bonzini wrote:
>On 30/04/19 05:44, Wei Yang wrote:
>> RAMBlock->offset is calculated by find_ram_offset, which makes sure the
>> offset is aligned to a word.
>>
>> This patch removes the alignment check on offset and unnecessary
>> variable *word*.
On 17/07/2019 20:21, Greg Kurz wrote:
On Wed, 17 Jul 2019 17:06:36 +1000
Alexey Kardashevskiy wrote:
The pseries guests do not normally allocate PCI resources and rely on
the system firmware doing so. Furthermore at least at some point in
the past the pseries guests won't even allowed to
On Wed, Jul 17, 2019 at 11:16:19AM +0200, Paolo Bonzini wrote:
>On 17/07/19 03:13, Wei Yang wrote:
>> On Tue, May 14, 2019 at 03:21:08PM +0100, Dr. David Alan Gilbert wrote:
>>> * Wei Yang (richardw.y...@linux.intel.com) wrote:
Since start of cpu_physical_memory_sync_dirty_bitmap is always 0,
Patch 1 refine bitmap_set a little.
Patch 2 add related test case to bitmap_set.
v3:
* free bmap
* all 1's set correctly
* expand range to 2 long
* check each possible of offset
* add a skeleton to test both bitmap_set and bitmap_set_atomic
v2:
* refine bitmap_set_atomic
* add a
The value left in nr is the number of bits for the last word, which
could be calculate the last word mask directly.
Remove the unnecessary size.
Signed-off-by: Wei Yang
---
v2: refine bitmap_set_atomic too, suggested from Peter
---
util/bitmap.c | 9 +++--
1 file changed, 3 insertions(+),
Add a test for bitmap_set. There are three cases:
* Both start and end is BITS_PER_LONG aligned
* Only start is BITS_PER_LONG aligned
* Only end is BITS_PER_LONG aligned
Signed-off-by: Wei Yang
---
v3:
* free bmap
* all 1's set correctly
* expand range to 2 long
* check each
Patchew URL:
https://patchew.org/QEMU/20190717071114.14772-1-richardw.y...@linux.intel.com/
Hi,
This series failed the asan build test. Please find the testing commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
On Tue, Jul 16, 2019 at 10:21 PM Chih-Min Chao wrote:
>
>
>
> On Wed, Jul 17, 2019 at 6:59 AM Alistair Francis wrote:
>>
>> On Tue, Jul 16, 2019 at 2:50 PM Philippe Mathieu-Daudé
>> wrote:
>> >
>> > On 7/16/19 10:43 PM, Alistair Francis wrote:
>> > > On Tue, Jul 16, 2019 at 6:56 AM Chih-Min
On Wed, Jul 10, 2019 at 10:40 AM Marc-André Lureau
wrote:
> I am not very familiar with podman or docker, so I am not able to tell
> you why docker does work by default. @Debarshi Ray might know, as he
> helped me finding a workaround.
You need to mention the UID mapping via --uidmap arguments
Hey,
Sorry for the late response. I was on vacation and away from my keyboard.
On Tue, Jul 9, 2019 at 9:44 PM Marc-André Lureau
wrote:
> With current podman, we have to use a uidmap trick in order to be able
> to rw-share the ccache directory with the container user.
>
> With a user 1000, the
Added a new boolean argument to blkconf_apply_backend_options()
to let the common block code know whether the chosen block
backend can handle zoned block devices or not.
blkconf_apply_backend_options() then sets BLK_PERM_SUPPORT_ZONED
permission accordingly. The raw code can then use this
Abort opening a zoned device as a raw file in case the chosen
block backend driver lacks proper support for this type of
storage.
Signed-off-by: Dmitry Fomichev
---
block/file-posix.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/block/file-posix.c b/block/file-posix.c
Currently, attaching zoned block devices (i.e. storage devices
compliant to ZAC/ZBC standards) using several virtio methods doesn't
work properly as zoned devices appear as regular block devices at the
guest. This may cause unexpected i/o errors and, potentially, some
data corruption.
To be more
From: Shin'ichiro Kawasaki
When READ CAPACITY command completes, scsi_read_complete() function
snoops the command result and updates SCSIDevice members blocksize and
max_lba . However, this update is executed even when READ CAPACITY
command indicates an error in sense data. This causes
The purpose of this patch is to recognize a zoned block device (ZBD)
when it is opened as a raw file. The new code initializes the zoned
model propery introduced by the previous commit.
This commit is Linux-specific as it gets the Zoned Block Device Model
value (none/host-managed/host-aware) from
This commit adds Zoned Device Model (as defined in T10 ZBC and
T13 ZAC standards) as a block driver property, along with some
useful access functions.
A new backend driver permission, BLK_PERM_SUPPORT_ZONED, is also
introduced. Only the drivers having this permission will be allowed
to open zoned
On 7/17/19 1:39 PM, John Snow wrote:
> From: Vladimir Sementsov-Ogievskiy
>
> Let's add a possibility to query dirty-bitmaps not only on root nodes.
> It is useful when dealing both with snapshots and incremental backups.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> [Added deprecation
These patches are based on ppc-for-4.2 and are also available at:
https://github.com/mdroth/qemu/commits/spapr-tpm-hcall-v2
This patchset implements the H_TPM_COMM hypercall, which provides a way
for an Ultravisor to pass raw TPM commands on to a host's TPM device,
either directly or through a
For now this only covers hcalls relating to TPM communication since
it's the only one particularly important from a QEMU perspective atm,
but others can be added here where it makes sense.
The full specification for all hcalls/ucalls will eventually be made
available in the public/OpenPower
This implements the H_TPM_COMM hypercall, which is used by an
Ultravisor to pass TPM commands directly to the host's TPM device, or
a TPM Resource Manager associated with the device.
This also introduces a new virtual device, spapr-tpm-proxy, which
is used to configure the host TPM path to be
Hi Philippe,
Sorry for the delay; I was away for a few weeks visiting family.
On Mon, Jul 01, 2019 at 08:06:21PM +0200, Philippe Mathieu-Daudé wrote:
> The difference with the previous content is now we have
> two new holes:
>
> - 0x0200-0x1000
> - 0x14001000-0x1c00
>
>
Quoting David Gibson (2019-07-16 21:01:15)
> On Tue, Jul 16, 2019 at 06:53:13PM -0500, Michael Roth wrote:
> > This implements the H_TPM_COMM hypercall, which is used by an
> > Ultravisor to pass TPM commands directly to the host's TPM device, or
> > a TPM Resource Manager associated with the
Quoting David Gibson (2019-07-16 20:29:12)
> On Tue, Jul 16, 2019 at 11:30:01AM -0500, Michael Roth wrote:
> > Quoting David Gibson (2019-07-14 21:25:24)
> > > On Fri, Jul 12, 2019 at 09:34:46AM -0500, Michael Roth wrote:
> > > > Quoting David Gibson (2019-07-12 01:46:19)
> > > > > On Thu, Jul 11,
On 7/17/19 4:05 PM, Eric Blake wrote:
> On 7/17/19 2:21 PM, John Snow wrote:
>>>
>>> Is this worth squeezing into 4.1, to start the deprecation clock one
>>> cycle earlier (on the grounds that the missing information for anonymous
>>> nodes is a bug)? Or am I pushing the boundaries too far,
On 7/17/19 2:21 PM, John Snow wrote:
>>
>> Is this worth squeezing into 4.1, to start the deprecation clock one
>> cycle earlier (on the grounds that the missing information for anonymous
>> nodes is a bug)? Or am I pushing the boundaries too far, where keeping
>> this as 4.2 material remains the
On 7/17/19 2:20 PM, Aleksandar Markovic wrote:
> But, does "configure" list somewhere unmet soft dependencies? (the
> question is general, not looking at SDL only) Is there any other way for
> an end user to have info on unmet dependencies (whether soft or hard),
> other than see QEMU is not
Am 17.07.2019 um 21:03 hat Sam Eiderman geschrieben:
> Gentle ping.
Through which tree is this supposed to go? I feel this is more firmware
interface related than block layer stuff.
Kevin
> > On 8 Jul 2019, at 20:30, Sam Eiderman wrote:
> >
> > Thanks Gerd,
> >
> > Gentle ping on this.
> >
On 7/15/19 8:01 PM, John Snow wrote:
> Based-on: https://github.com/jnsnow/qemu/tree/bitmaps
>
> This follows the previous series which adds the 'bitmap' sync mode
> and uses it to add interactions with bitmaps to the 'full' and 'top'
> modes to blockdev-backup and drive-backup.
>
> Why?
>
On 7/17/19 3:13 PM, Eric Blake wrote:
> On 7/17/19 12:39 PM, John Snow wrote:
>> From: Vladimir Sementsov-Ogievskiy
>>
>> Let's add a possibility to query dirty-bitmaps not only on root nodes.
>> It is useful when dealing both with snapshots and incremental backups.
>>
>> Signed-off-by:
On Wed, Jul 17, 2019 at 8:57 PM Eric Blake wrote:
>
> On 7/17/19 1:34 PM, Aleksandar Markovic wrote:
>
> >
> > Daniel, that is fine, I don't question that, I basically wanted to start a
> > talk
> > between us to clarify some things. Related to our situation in the field,
> > I have a
On 7/17/19 12:39 PM, John Snow wrote:
> From: Vladimir Sementsov-Ogievskiy
>
> Let's add a possibility to query dirty-bitmaps not only on root nodes.
> It is useful when dealing both with snapshots and incremental backups.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> [Added deprecation
In struct OptsVisitor, repeated_opts member points to a list in the
unprocessed_opts hash table after the list has been destroyed. A
subsequent call to visit_type_int() references the deleted list. It
results in use-after-free issue. Also, the Visitor object call back
functions are supposed to set
Gentle ping.
Sam
> On 8 Jul 2019, at 20:30, Sam Eiderman wrote:
>
> Thanks Gerd,
>
> Gentle ping on this.
>
> Sam
>
>> On 1 Jul 2019, at 10:41, Gerd Hoffmann wrote:
>>
>> On Wed, Jun 26, 2019 at 03:39:40PM +0300, Sam Eiderman wrote:
>>> v1:
>>>
>>> Non-standard logical geometries break
On 7/17/19 1:34 PM, Aleksandar Markovic wrote:
>
> Daniel, that is fine, I don't question that, I basically wanted to start a
> talk
> between us to clarify some things. Related to our situation in the field,
> I have a sub-question to you:
>
> Let's say there is a build system with SDL 1.2,
On Wed, Jul 17, 2019 at 01:39:01PM +0800, Tao Xu wrote:
> Hi Eduardo,
>
> Could I ask a question about introducing a old CPU model? Maybe not so old
> because it was launched in 2017. It is the former generation (Atom Server)
> of Snowridge and if this cpu model be added, qemu may can migrate
On Tue, Jul 16, 2019 at 7:44 PM Daniel P. Berrangé wrote:
>
> On Tue, Jul 16, 2019 at 07:09:37PM +0200, Aleksandar Markovic wrote:
> > On Tue, Jul 16, 2019 at 1:54 PM Thomas Huth wrote:
> > >
> > > On 16/07/2019 13.17, Aleksandar Markovic wrote:
> > > > Hello, Gerd, Daniel, and others involved.
Am 17.07.2019 um 15:43 schrieb Alex Bennée:
> From: Philippe Mathieu-Daudé
>
> Various firmwares has been added in the pc-bios/ directory:
>
> - CCW (since commit 0c1fecdd523)
> - Skiboot (since commit bcad45de6a0)
> - EDK2(since commit f7fa38b74c3)
>
> Since we install qemu-system able
On 7/16/19 12:11 PM, Max Reitz wrote:
> On 16.07.19 18:02, John Snow wrote:
>>
>>
>> On 7/16/19 7:43 AM, Max Reitz wrote:
>>> On 16.07.19 02:01, John Snow wrote:
Presently, If sync=TOP is selected, we mark the entire bitmap as dirty.
In the write notifier handler, we dutifully copy
On 7/17/19 5:50 AM, Max Reitz wrote:
> On 16.07.19 18:58, John Snow wrote:
>>
>>
>> On 7/16/19 8:04 AM, Max Reitz wrote:
>>> On 16.07.19 02:01, John Snow wrote:
Signed-off-by: John Snow
---
tests/qemu-iotests/257 | 41 +-
tests/qemu-iotests/257.out | 3089
On 7/17/19 1:39 PM, John Snow wrote:
> From: Vladimir Sementsov-Ogievskiy
>
> Let's add a possibility to query dirty-bitmaps not only on root nodes.
> It is useful when dealing both with snapshots and incremental backups.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> [Added deprecation
From: Vladimir Sementsov-Ogievskiy
Let's add a possibility to query dirty-bitmaps not only on root nodes.
It is useful when dealing both with snapshots and incremental backups.
Signed-off-by: Vladimir Sementsov-Ogievskiy
[Added deprecation information. --js]
Signed-off-by: John Snow
---
On Wed, 17 Jul 2019 15:39:52 +1000
Nicholas Piggin wrote:
> This has been useful to modify and test the Linux pseries suspend
> code but it requires modification to the guest to call it (due to
> being gated by other unimplemented features). It is not otherwise
> used by Linux yet, but work is
On Wed, 17 Jul 2019 15:39:51 +1000
Nicholas Piggin wrote:
> This does not do directed yielding and is not quite as strict as PAPR
> specifies in terms of precise dispatch behaviour. This generally will
> mean suboptimal performance, rather than guest misbehaviour. Linux
> does not rely on exact
On 7/11/19 3:32 PM, Jan Bobek wrote:
> The --xfeatures option is modelled after identically-named option to
> RISU itself; it allows the user to specify which vector registers
> should be initialized, so that the test image doesn't try to access
> registers which may not be present at runtime.
On 7/11/19 3:32 PM, Jan Bobek wrote:
> This flag instructs the x86 backend to emit 64-bit (rather than
> 32-bit) code.
>
> Signed-off-by: Jan Bobek
> ---
> risugen | 7 ++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
Reviewed-by: Richard Henderson
r~
Patchew URL: https://patchew.org/QEMU/20190716161901.1430-1-mlevi...@redhat.com/
Hi,
This series failed the asan build test. Please find the testing commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
make
Which QEMU version are you using here? Can you reproduce this issue with
the latest upstream QEMU ? ... otherwise, please report this issue to
the Debian bug tracker instead.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
On 17/07/2019 15.43, Alex Bennée wrote:
> Commit 97fd1ea8c1 broke the build for --without-default-devices as
> VMMOUSE depends on VMPORT.
>
> Fixes: 97fd1ea8c1
> Signed-off-by: Alex Bennée
> ---
> hw/i386/Kconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git
On 7/16/19 11:26 AM, John Snow wrote:
>
>
> On 7/16/19 2:32 AM, Markus Armbruster wrote:
>> John Snow writes:
>>
>>> On 6/5/19 8:46 AM, Markus Armbruster wrote:
John Snow writes:
> On 5/31/19 10:55 AM, Eric Blake wrote:
>> On 5/30/19 11:26 AM, John Snow wrote:
>>>
ping.
On Fri, Jul 12, 2019 at 8:37 AM Michael Rolnik wrote:
> This series of patches adds 8bit AVR cores to QEMU.
> All instruction, except BREAK/DES/SPM/SPMX, are implemented. Not fully
> tested yet.
> However I was able to execute simple code with functions. e.g fibonacci
> calculation.
>
On Wed, Jun 26, 2019 at 03:52:44PM +0200, Andrew Jones wrote:
> On Wed, Jun 26, 2019 at 12:20:29PM +0200, Richard Henderson wrote:
> > On 6/21/19 6:34 PM, Andrew Jones wrote:
> > > Since 97a28b0eeac14 ("target/arm: Allow VFP and Neon to be disabled via
> > > a CPU property") we can disable the
On Wed, 17 Jul 2019 15:39:49 +1000
Nicholas Piggin wrote:
> Implement cpu_exec_enter/exit on ppc which calls into new methods of
> the same name in PPCVirtualHypervisorClass. These are used by spapr
> to implement these splpar elements, used in subsequent changes.
>
> Signed-off-by: Nicholas
Although arguably the line:
gemu_log("Unsupported setsockopt level=%d optname=%d\n", level,
optname);
Could be
qemu_log_mask(LOG_UNIMP,)
Not sure where gemu_log is used, it seems to be strace related.
--
You received this bug notification because you are a member of qemu-
devel-ml,
The -d/-D options should work in linux-user as well. You can also set
QEMU_LOG_FILENAME and QEMU_LOG environment variables. Do these not work
for you?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Is this fixed now? Can we mark as 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/1829576
Title:
QEMU-SYSTEM-PPC64 Regression QEMU-4.0.0
Status in QEMU:
New
Bug description:
I
Does "make check-tcg" work in this case? It works for me here.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1835693
Title:
s390x binaries
Have you got a test case? The check-tcg tests all pass and they are
statically linked elfs.
** Tags added: linux-user
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
On 07/17/19 15:46, Peter Maydell wrote:
> On Wed, 17 Jul 2019 at 14:36, Philippe Mathieu-Daudé
> wrote:
>> I still wonder why this didn't assert on Peter's setup.
>
> My setup does not assert because my host kernel correctly
> provides the ID register values to QEMU. Laszlo's appears
> to be
On 17/07/19 16:54, Collin Walling wrote:
> PCI host plugging will check for the MSI-X capability on the
> PCI device. If the MSI-X cap is missing, we fail device plugging.
> We do not check for MSI. Only MSI-X.
>
> Specifically, the capability is represented by PCI_CAP_ID_MSIX
> in pci_regs.h
** Tags added: linux-user s390x tcg
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1835693
Title:
s390x binaries segfault
Status in QEMU:
Incomplete
Bug description:
Hello World appears to
On Wed, 17 Jul 2019 03:20:55 -0500
Shivaprasad G Bhat wrote:
> The check to see if the idle_timer is already initialized is
> missing. Every vcpu thread would call kvm_arch_init_vcpu()
> and overwrite the idle_timer resulting in a memory leak.
> Patch fixes that.
>
> Signed-off-by: Shivaprasad
From: Aleksandar Markovic
Structure ucontext for MIPS is defined in the following way in
Linux kernel:
(arch/mips/include/uapi/asm/ucontext.h, lines 54-64)
struct ucontext {
/* Historic fields matching asm-generic */
unsigned long uc_flags;
struct ucontext *uc_link;
From: Daniel P. Berrangé
The SIOCGSTAMP symbol was previously defined in the
asm-generic/sockios.h header file. QEMU sees that header
indirectly via sys/socket.h
In linux kernel commit 0768e17073dc527ccd18ed5f96ce85f9985e9115
the asm-generic/sockios.h header no longer defines SIOCGSTAMP.
From: Rémi Denis-Courmont
Fix a crash with LTP testsuite and aarch64:
tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
qemu-aarch64: .../qemu/accel/tcg/translate-all.c:2522: page_check_range:
Assertion `start < ((target_ulong)1 << L1_MAP_ADDR_SPACE_BITS)' failed.
On 7/17/19 9:52 AM, Paolo Bonzini wrote:
On 17/07/19 14:59, Collin Walling wrote:
On 7/16/19 11:04 AM, Thomas Huth wrote:
On 16/07/2019 15.06, Markus Armbruster wrote:
Paolo Bonzini writes:
On 15/07/19 18:12, Cornelia Huck wrote:
Is it INTx vs. MSI vs. MSI-X?
I think for s390x we need
The following changes since commit a1a4d49f60d2b899620ee2be4ebb991c4a90a026:
Merge remote-tracking branch
'remotes/philmd-gitlab/tags/pflash-next-20190716' into staging (2019-07-16
17:02:44 +0100)
are available in the Git repository at:
git://github.com/vivier/qemu.git
On Tue, 16 Jul 2019 16:38:11 +0100
Shameer Kolothum wrote:
> This is in preparation to create ACPI GED device as we
> need to disable it for <4.2 for migration to work.
>
> Signed-off-by: Shameer Kolothum
Reviewed-by: Igor Mammedov
> ---
> hw/arm/virt.c | 9 -
>
On 7/17/19 3:43 PM, Alex Bennée wrote:
> From: Philippe Mathieu-Daudé
>
> Various firmwares has been added in the pc-bios/ directory:
>
> - CCW (since commit 0c1fecdd523)
> - Skiboot (since commit bcad45de6a0)
> - EDK2(since commit f7fa38b74c3)
>
> Since we install qemu-system able to
On Tue, 16 Jul 2019 16:38:10 +0100
Shameer Kolothum wrote:
> 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 through DT or ACPI and hence both cold/hot plug of memory
> is explicitly
The halt poll control MSR should only be enabled on hosts which
support it.
Fixes: ("kvm: i386: halt poll control MSR support")
Signed-off-by: Mark Kanda
---
v2: Remove unnecessary hunks which break migration with older hosts (Paolo)
---
target/i386/cpu.c | 1 -
1 file changed, 1 deletion(-)
On Tue, 16 Jul 2019 16:38:09 +0100
Shameer Kolothum wrote:
> 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
>
On 7/16/19 11:08 PM, tony.ngu...@bt.com wrote:
> diff --git a/accel/tcg/cputlb.c b/accel/tcg/cputlb.c
> index baa61719ad..11debb7dda 100644
> --- a/accel/tcg/cputlb.c
> +++ b/accel/tcg/cputlb.c
> @@ -731,7 +731,7 @@ void tlb_set_page_with_attrs(CPUState *cpu, target_ulong
> vaddr,
>
On Wed, Jul 17, 2019 at 08:30:29PM +0800, Jason Wang wrote:
>
> On 2019/7/17 下午7:00, Michael S. Tsirkin wrote:
> > On Wed, Jun 12, 2019 at 10:11:57AM +0800, Tiwei Bie wrote:
> > > On Tue, Jun 11, 2019 at 10:10:14AM -0400, Michael S. Tsirkin wrote:
> > > > On Tue, Jun 11, 2019 at 02:51:37PM +0800,
On 7/16/19 11:06 PM, tony.ngu...@bt.com wrote:
> +++ b/include/exec/poison.h
> @@ -38,7 +38,6 @@
> #pragma GCC poison TARGET_HAS_BFLT
> #pragma GCC poison TARGET_NAME
> #pragma GCC poison TARGET_SUPPORTS_MTTCG
> -#pragma GCC poison TARGET_WORDS_BIGENDIAN
You can't do this. This is here for a
On 7/16/19 11:04 PM, tony.ngu...@bt.com wrote:
> +MO_ASHIFT = 4,
> +MO_AMASK = 7 << MO_ASHIFT,
> +#ifdef ALIGNED_ONLY
> +MO_ALIGN = 0,
> +MO_UNALN = MO_AMASK,
> +#else
> +MO_ALIGN = MO_AMASK,
> +MO_UNALN = 0,
> +#endif
I'm not sure you can move this portion as-is.
I think
Hi Laszlo,
On 7/17/19 2:24 PM, Laszlo Ersek wrote:
> Hi Phil,
>
> On 07/17/19 00:15, Philippe Mathieu-Daudé wrote:
>> Hello it's me again, insisting with this series because there are at
>> least 2 different report of guests bricked on reset due to the bug
>> fixed by patch #5:
>>
From: Thomas Huth
Remove some more tests from the "auto" group that either have issues
in certain environments (like macOS or FreeBSD, or on certain file systems
like ZFS or tmpfs), do not work with the qcow2 format, or that are simply
taking too much time.
Reviewed-by: Max Reitz
From: Philippe Mathieu-Daudé
The NSIS installer generates an executable suitable to install
QEMU on Windows.
Suggested-by: Alex Bennée
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20190715174817.18981-9-phi...@redhat.com>
[AJB: also --enable-docs in configure step]
Signed-off-by: Alex
1 - 100 of 240 matches
Mail list logo
