On Wed, Mar 07, 2018 at 08:34:24PM +0800, Wei Wang wrote:
> The new feature enables the virtio-balloon device to receive hints of
> guest free pages from the free page vq.
>
> balloon_free_page_start - start guest free page hint reporting.
> balloon_free_page_stop - stop guest free page hint
From: John Snow
Signed-off-by: John Snow
Signed-off-by: Kevin Wolf
---
tests/qemu-iotests/056 | 187 +
tests/qemu-iotests/056.out | 4 +-
2 files changed, 189 insertions(+), 2 deletions(-)
> From: Qemu-devel bounces+andrew.baumann=microsoft@nongnu.org> On Behalf Of Peter
> Maydell
> Sent: Tuesday, 13 March 2018 08:35
>
> For the rpi1 and 2 we want to boot the Linux kernel via some
> custom setup code that makes sure that the SMC instruction
> acts as a no-op, because it's used
> From: Peter Maydell
> Sent: Tuesday, 13 March 2018 08:35
>
> The BCM2837 sets the Aff1 field of the MPIDR affinity values for the
> CPUs to 0, whereas the BCM2836 uses 0xf. Set this correctly, as it
> is required for Linux to boot.
>
> Signed-off-by: Peter Maydell
This adds the .bdrv_co_create driver callback to vpc, which
enables image creation over QMP.
Signed-off-by: Kevin Wolf
Reviewed-by: Max Reitz
---
qapi/block-core.json | 33 ++-
block/vpc.c | 152
Everything that refers to the protocol layer or QemuOpts is moved out of
block_crypto_create_generic(), so that the remaining function is
suitable to be called by a .bdrv_co_create implementation.
LUKS is the only driver that actually implements the old interface, and
we don't intend to use it in
On Tue, 13 Mar 2018 13:56:16 +0100
Paolo Bonzini wrote:
> The following changes since commit fb5fff15881ba7a002924b967eb211c002897983:
>
> Merge remote-tracking branch
> 'remotes/kraxel/tags/vga-20180312-pull-request' into staging (2018-03-12
> 18:35:37 +)
>
> are
This adds the .bdrv_co_create driver callback to vhdx, which
enables image creation over QMP.
Signed-off-by: Kevin Wolf
Reviewed-by: Max Reitz
---
qapi/block-core.json | 40 +-
block/vhdx.c | 216
The following changes since commit 22ef7ba8e8ce7fef297549b3defcac333742b804:
Merge remote-tracking branch 'remotes/famz/tags/staging-pull-request' into
staging (2018-03-13 11:42:45 +)
are available in the Git repository at:
https://github.com/stsquad/qemu.git
From: John Snow
For jobs utilizing the new manual workflow, we intend to prohibit
them from modifying the block graph until the management layer provides
an explicit ACK via block-job-finalize to move the process forward.
To distinguish this runstate from "ready" or "waiting,"
On 03/07/2018 02:25 AM, Alberto Garcia wrote:
SCSI controllers are no longer created automatically for
-drive if=scsi, so this patch updates the tests that relied
on that.
Signed-off-by: Alberto Garcia
---
tests/qemu-iotests/051.pc.out | 20
Signed-off-by: Kevin Wolf
Reviewed-by: Daniel P. Berrangé
---
tests/qemu-iotests/209 | 210 +++
tests/qemu-iotests/209.out | 136
tests/qemu-iotests/common.rc | 2 +-
From: John Snow
For jobs that are stuck waiting on others in a transaction, it would
be nice to know that they are no longer "running" in that sense, but
instead are waiting on other jobs in the transaction.
Jobs that are "waiting" in this sense cannot be meaningfully altered
QEMU SCSI code makes assumptions about how the PROTECT and BYTCHK
works in the protocol, denying support for PI (Protection
Information) in case the guest OS requests it. However, in SCSI versions 2
and older, there is no PI concept in the protocol.
This means that when dealing with such devices:
This adds the .bdrv_co_create driver callback to qcow, which
enables image creation over QMP.
Signed-off-by: Kevin Wolf
Reviewed-by: Max Reitz
Reviewed-by: Jeff Cody
---
qapi/block-core.json | 21 +-
block/qcow.c | 196
From: Fam Zheng
Reopen flags are not synchronized according to the
bdrv_reopen_queue_child precedence until bdrv_reopen_prepare. It is a
bit too late: we already check the consistency in bdrv_check_perm before
that.
This fixes the bug that when bdrv_reopen a RO node as RW, the
From: John Snow
Some jobs upon finalization may need to perform some work that can
still fail. If these jobs are part of a transaction, it's important
that these callbacks fail the entire transaction.
We allow for a new callback in addition to commit/abort/clean that
allows us
This adds the .bdrv_co_create driver callback to qed, which
enables image creation over QMP.
Signed-off-by: Kevin Wolf
Reviewed-by: Max Reitz
---
qapi/block-core.json | 25 ++-
block/qed.c | 204
From: Fam Zheng
Signed-off-by: Fam Zheng
Reviewed-by: Max Reitz
Signed-off-by: Kevin Wolf
---
tests/qemu-iotests/153 | 12
tests/qemu-iotests/153.out | 5 +
2 files changed, 17 insertions(+)
diff
On Wed, Mar 07, 2018 at 08:34:25PM +0800, Wei Wang wrote:
> Start the free page optimization after the migration bitmap is
> synchronized. This can't be used in the stop phase since the guest
> is paused. Make sure the guest reporting has stopped before
> synchronizing the migration dirty bitmap.
From: John Snow
Presently, even if a job is canceled post-completion as a result of
a failing peer in a transaction, it will still call .commit because
nothing has updated or changed its return code.
The reason why this does not cause problems currently is because
backup's
From: Max Reitz
Signed-off-by: Max Reitz
Signed-off-by: Kevin Wolf
---
block/vdi.c | 46 --
1 file changed, 28 insertions(+), 18 deletions(-)
diff --git a/block/vdi.c b/block/vdi.c
index
The crypto driver used to create the image file in a callback from the
crypto subsystem. If we want to implement .bdrv_co_create, this needs to
go away because that callback will get a reference to an already
existing block node.
Move the image file creation to block_crypto_create_generic().
On Tue, Mar 13, 2018 at 04:20:19PM +, Peter Maydell wrote:
> On 12 March 2018 at 20:12, Daniel P. Berrangé wrote:
> > The following changes since commit 819fd4699c7b36d574292bcbd8bc25e9d716c84b:
> >
> > Merge remote-tracking branch
> >
From: John Snow
For jobs that have reached their CONCLUDED state, prior to having their
last reference put down (meaning jobs that have completed successfully,
unsuccessfully, or have been canceled), allow the user to dismiss the
job's lingering status report via
From: Max Reitz
In preparation of QAPI-fying VDI image creation, we have to create a
BlockdevCreateOptionsVdi type which is received by a (future)
vdi_co_create().
vdi_co_create_opts() now converts the QemuOpts object into such a
BlockdevCreateOptionsVdi object. The
The .bdrv_getlength implementation of the crypto block driver asserted
that the payload offset isn't after EOF. This is an invalid assertion to
make as the image file could be corrupted. Instead, check it and return
-EIO if the file is too small for the payload offset.
Zero length images are
On 13.03.2018 17:08, Kevin Wolf wrote:
> Am 06.03.2018 um 17:52 hat Thomas Huth geschrieben:
>> On 06.03.2018 17:45, Alberto Garcia wrote:
>>> Signed-off-by: Alberto Garcia
>>> ---
>>> tests/qemu-iotests/051.pc.out | 20
>>> tests/qemu-iotests/186.out|
From: John Snow
The completed_single function is getting a little mucked up with
checking to see which callbacks exist, so let's factor them out.
Signed-off-by: John Snow
Reviewed-by: Eric Blake
Reviewed-by: Kevin Wolf
This adds the .bdrv_co_create driver callback to luks, which enables
image creation over QMP.
Signed-off-by: Kevin Wolf
Reviewed-by: Daniel P. Berrangé
---
qapi/block-core.json | 17 -
block/crypto.c | 34
From: John Snow
Whatever the state a blockjob is in, it should be able to be canceled
by the block layer.
Signed-off-by: John Snow
Signed-off-by: Kevin Wolf
---
tests/test-blockjob.c | 233
From: John Snow
Add a new state that specifically demarcates when we begin to permanently
demolish a job after it has performed all work. This makes the transition
explicit in the STM table and highlights conditions under which a job may
be demolished.
Alongside this state,
This adds the .bdrv_co_create driver callback to parallels, which
enables image creation over QMP.
Signed-off-by: Kevin Wolf
Reviewed-by: Max Reitz
Reviewed-by: Jeff Cody
---
qapi/block-core.json | 18 -
block/parallels.c| 199
From: John Snow
Simply apply a function transaction-wide.
A few more uses of this in forthcoming patches.
Signed-off-by: John Snow
Signed-off-by: Kevin Wolf
---
blockjob.c | 25 -
1 file changed, 16 insertions(+),
From: John Snow
Instead of automatically transitioning from PENDING to CONCLUDED, gate
the .prepare() and .commit() phases behind an explicit acknowledgement
provided by the QMP monitor if auto_finalize = false has been requested.
This allows us to perform graph changes in
From: John Snow
model all independent jobs as single job transactions.
It's one less case we have to worry about when we add more states to the
transition machine. This way, we can just treat all job lifetimes exactly
the same. This helps tighten assertions of the STM graph
This makes the .bdrv_co_create(_opts) implementation of vdi look more
like the other recently converted block drivers.
Signed-off-by: Kevin Wolf
Reviewed-by: Max Reitz
---
block/vdi.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff
From: John Snow
add a new state "CONCLUDED" that identifies a job that has ceased all
operations. The wording was chosen to avoid any phrasing that might
imply success, error, or cancellation. The task has simply ceased all
operation and can never again perform any work.
From: John Snow
The state transition table has mostly been implied. We're about to make
it a bit more complex, so let's make the STM explicit instead.
Perform state transitions with a function that for now just asserts the
transition is appropriate.
Transitions:
Undefined ->
From: John Snow
Trivial; Document what the job creation flags do,
and some general tidying.
Signed-off-by: John Snow
Signed-off-by: Kevin Wolf
---
include/block/blockjob.h | 8
include/block/blockjob_int.h | 4 +++-
2 files
Originally we added parallels as a read-only format to qemu-iotests
where we did just some tests with a binary image. Since then, write and
image creation support has been added to the driver, so we can now
enable it in _supported_fmt generic.
The driver doesn't support migration yet, though, so
From: John Snow
Split out the pause command into the actual pause and the wait.
Not every usage presently needs to resubmit a pause request.
The intent with the next commit will be to explicitly disallow
redundant or meaningless pause/resume requests, so the tests
need to
From: John Snow
Which commands ("verbs") are appropriate for jobs in which state is
also somewhat burdensome to keep track of.
As of this commit, it looks rather useless, but begins to look more
interesting the more states we add to the STM table.
A recurring theme is that no
From: John Snow
If speed is '0' it's not actually "less than" the previous speed.
Kick the job in this case too.
Signed-off-by: John Snow
Reviewed-by: Eric Blake
Reviewed-by: Kevin Wolf
Signed-off-by: Kevin Wolf
From: Max Reitz
Signed-off-by: Max Reitz
Signed-off-by: Kevin Wolf
---
qapi/block-core.json | 2 +-
block/vdi.c | 24 +++-
2 files changed, 20 insertions(+), 6 deletions(-)
diff --git a/qapi/block-core.json
From: John Snow
Add a new state ABORTING.
This makes transitions from normative states to error states explicit
in the STM, and serves as a disambiguation for which states may complete
normally when normal end-states (CONCLUDED) are added in future commits.
Notably,
On 2/28/18 20:41, Bastian Koppelmann wrote:
> On 02/28/2018 07:11 AM, Thomas Huth wrote:
>> On 27.02.2018 12:51, Peter Maydell wrote:
>>
>>> Possibly there are other target architectures we could reasonably
>>> deprecate-and-remove (though none of the other ones Linux is dropping
>>> in this
On 3/12/2018 5:59 AM, Gerd Hoffmann wrote:
Typically the scanline length and the line offset are identical. But
in case they are not our calculation for region_end is incorrect. Using
line_offset is fine for all scanlines, except the last one where we have
to use the actual scanline length.
On 03/13/2018 12:14 PM, Vladimir Sementsov-Ogievskiy wrote:
>
> Hmm, I agree, it is the simplest thing we can do for now, and I'll
> rethink later,
> how (and is it worth doing) to go to postcopy automatically in case of
> only-dirty-bitmaps.
> Should I respin?
Please do. I already staged
From: John Snow
We're about to add several new states, and booleans are becoming
unwieldly and difficult to reason about. It would help to have a
more explicit bookkeeping of the state of blockjobs. To this end,
add a new "status" field and add our existing states in a
Am 06.03.2018 um 17:52 hat Thomas Huth geschrieben:
> On 06.03.2018 17:45, Alberto Garcia wrote:
> > Signed-off-by: Alberto Garcia
> > ---
> > tests/qemu-iotests/051.pc.out | 20
> > tests/qemu-iotests/186.out| 22 +++---
> > 2 files
From: John Snow
Expose the "manual" property via QAPI for the backup-related jobs.
As of this commit, this allows the management API to request the
"concluded" and "dismiss" semantics for backup jobs.
Signed-off-by: John Snow
Signed-off-by: Kevin Wolf
13.03.2018 18:35, Dr. David Alan Gilbert wrote:
* Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote:
13.03.2018 13:30, Dr. David Alan Gilbert wrote:
* Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote:
12.03.2018 18:30, Dr. David Alan Gilbert wrote:
* Vladimir
The following changes since commit 22ef7ba8e8ce7fef297549b3defcac333742b804:
Merge remote-tracking branch 'remotes/famz/tags/staging-pull-request' into
staging (2018-03-13 11:42:45 +)
are available in the git repository at:
git://repo.or.cz/qemu/kevin.git tags/for-upstream
for you to
On Tue, Mar 13, 2018 at 04:48:26PM +0100, Gerd Hoffmann wrote:
> A driver to let userspace turn iovecs into dma-bufs.
>
> Use case: Allows qemu pass around dmabufs for the guest framebuffer.
> https://www.kraxel.org/cgit/qemu/log/?h=sirius/udmabuf has an
> experimental patch.
>
> Also allows
Using a local m68k floatx80_tan()
[copied from previous:
Written by Andreas Grabher for Previous, NeXT Computer Emulator.]
Signed-off-by: Laurent Vivier
Message-Id: <20180312202728.23790-2-laur...@vivier.eu>
---
target/m68k/fpu_helper.c| 5 +
13.03.2018 18:55, Eric Blake wrote:
On 03/12/2018 10:21 AM, Vladimir Sementsov-Ogievskiy wrote:
Hi all.
Here is minimal realization of base:allocation context of NBD
block-status extension, which allows to get block status through
NBD.
v2 changes are in each patch after "---" line.
Vladimir
On 12 March 2018 at 10:31, Abdallah Bouassida
wrote:
> This is a preparation for the coming feature of creating dynamically an XML
> description for the ARM sysregs.
> Add "_S" suffix to the secure version of sysregs that have both S and NS views
> Replace (S)
Using a local m68k floatx80_cosh()
[copied from previous:
Written by Andreas Grabher for Previous, NeXT Computer Emulator.]
Signed-off-by: Laurent Vivier
Message-Id: <20180312202728.23790-12-laur...@vivier.eu>
---
target/m68k/fpu_helper.c | 5 +++
target/m68k/helper.h |
Using a local m68k floatx80_asin()
[copied from previous:
Written by Andreas Grabher for Previous, NeXT Computer Emulator.]
Signed-off-by: Laurent Vivier
Message-Id: <20180312202728.23790-7-laur...@vivier.eu>
---
target/m68k/fpu_helper.c | 5
target/m68k/helper.h |
Using a local m68k floatx80_sin()
[copied from previous:
Written by Andreas Grabher for Previous, NeXT Computer Emulator.]
Signed-off-by: Laurent Vivier
Message-Id: <20180312202728.23790-3-laur...@vivier.eu>
---
target/m68k/fpu_helper.c | 5 +
target/m68k/helper.h | 1
Using a local m68k floatx80_atan()
[copied from previous:
Written by Andreas Grabher for Previous, NeXT Computer Emulator.]
Signed-off-by: Laurent Vivier
Message-Id: <20180312202728.23790-6-laur...@vivier.eu>
---
target/m68k/fpu_helper.c| 5 +
Using a local m68k floatx80_cos()
[copied from previous:
Written by Andreas Grabher for Previous, NeXT Computer Emulator.]
Signed-off-by: Laurent Vivier
Message-Id: <20180312202728.23790-4-laur...@vivier.eu>
---
target/m68k/fpu_helper.c | 5 +
target/m68k/helper.h | 1
Using a local m68k floatx80_sinh()
[copied from previous:
Written by Andreas Grabher for Previous, NeXT Computer Emulator.]
Signed-off-by: Laurent Vivier
Message-Id: <20180312202728.23790-11-laur...@vivier.eu>
---
target/m68k/fpu_helper.c | 5 +++
target/m68k/helper.h |
* Peter Xu (pet...@redhat.com) wrote:
> On Tue, Mar 13, 2018 at 12:35:56PM +, Dr. David Alan Gilbert wrote:
>
> [...]
>
> > > Yes I think if without OOB we should be fine since even the cleanup is
> > > running with the BQL.
> > >
> > > Now I don't have good idea to solve this problem
Using local m68k floatx80_tanh() and floatx80_etoxm1()
[copied from previous:
Written by Andreas Grabher for Previous, NeXT Computer Emulator.]
Signed-off-by: Laurent Vivier
Message-Id: <20180312202728.23790-10-laur...@vivier.eu>
---
target/m68k/fpu_helper.c | 5 +
using floatx80_sin() and floatx80_cos()
Signed-off-by: Laurent Vivier
Message-Id: <20180312202728.23790-5-laur...@vivier.eu>
---
target/m68k/fpu_helper.c | 11 +++
target/m68k/helper.h | 1 +
target/m68k/translate.c | 8
3 files changed, 20
The following changes since commit 59667bb167f773965ce6547352f312eff0d4d523:
Merge remote-tracking branch 'remotes/ehabkost/tags/x86-next-pull-request'
into staging (2018-03-13 14:02:47 +)
are available in the Git repository at:
git://github.com/vivier/qemu-m68k.git
Using a local m68k floatx80_acos()
[copied from previous:
Written by Andreas Grabher for Previous, NeXT Computer Emulator.]
Signed-off-by: Laurent Vivier
Message-Id: <20180312202728.23790-8-laur...@vivier.eu>
---
target/m68k/fpu_helper.c | 5
target/m68k/helper.h |
Using a local m68k floatx80_atanh()
[copied from previous:
Written by Andreas Grabher for Previous, NeXT Computer Emulator.]
Signed-off-by: Laurent Vivier
Message-Id: <20180312202728.23790-9-laur...@vivier.eu>
---
target/m68k/fpu_helper.c | 5
target/m68k/helper.h |
Am 13.03.2018 um 13:12 hat Jeff Cody geschrieben:
> From: Liang Li
>
> When doing drive mirror to a low speed shared storage, if there was heavy
> BLK IO write workload in VM after the 'ready' event, drive mirror block job
> can't be canceled immediately, it would
On Tue, Mar 13, 2018 at 12:35:56PM +, Dr. David Alan Gilbert wrote:
[...]
> > Yes I think if without OOB we should be fine since even the cleanup is
> > running with the BQL.
> >
> > Now I don't have good idea to solve this problem except introducing a
> > lock. How about I add a patch to
On 03/12/2018 10:21 AM, Vladimir Sementsov-Ogievskiy wrote:
Hi all.
Here is minimal realization of base:allocation context of NBD
block-status extension, which allows to get block status through
NBD.
v2 changes are in each patch after "---" line.
Vladimir Sementsov-Ogievskiy (8):
* Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote:
> 13.03.2018 13:30, Dr. David Alan Gilbert wrote:
> > * Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote:
> > > 12.03.2018 18:30, Dr. David Alan Gilbert wrote:
> > > > * Vladimir Sementsov-Ogievskiy
On Tue, Mar 13, 2018 at 3:25 PM, nee wrote:
> On Mon, Mar 12, 2018 at 1:21 PM, Greg Kurz wrote:
>> On Mon, 12 Mar 2018 13:08:29 +
>> Daniel P. Berrangé wrote:
>>
>>> On Mon, Mar 12, 2018 at 02:02:29PM +0100, Greg Kurz wrote:
>>> >
On 03/12/2018 10:21 AM, Vladimir Sementsov-Ogievskiy wrote:
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
+
+iotests.verify_image_format(supported_fmts=['qcow2'])
Interesting that './check -nbd' doesn't run 209 (because that defaults
to format -raw, but we
A driver to let userspace turn iovecs into dma-bufs.
Use case: Allows qemu pass around dmabufs for the guest framebuffer.
https://www.kraxel.org/cgit/qemu/log/?h=sirius/udmabuf has an
experimental patch.
Also allows qemu to export guest virtio-gpu resources as host dmabufs.
Should be possible
Our BCM2836 type is really a generic one that can be any of
the bcm283x family. Rename it accordingly. We change only
the names which are visible via the header file to the
rest of the QEMU code, leaving private function names
in bcm2836.c as they are.
This is a preliminary to making bcm283x be
On 03/12/2018 10:21 AM, Vladimir Sementsov-Ogievskiy wrote:
Simple way to have auto generated filenames with auto cleanup. Like
FilePath but without using 'with' statement and without additional
indentation of the whole test.
Signed-off-by: Vladimir Sementsov-Ogievskiy
The bcm2837 is pretty similar to the bcm2836, but it does have
some differences. Notably, the MPIDR affinity aff1 values it
sets for the CPUs are 0x0, rather than the 0xf that the bcm2836
uses, and if this is wrong Linux will not boot.
Rather than trying to have one device with properties that
On Tue, Mar 13, 2018 at 03:32:10PM +, Alex Bennée wrote:
> The tools are already built elsewhere so we might as well not build it
> here as we just need to test the modules build of QEMU itself.
>
> Signed-off-by: Alex Bennée
> ---
> .travis.yml | 2 +-
> 1 file
I had a go at booting Debian's Linux kernel on our raspi3 model.
These patches fix a variety of bugs that were stopping that working:
* the board was trying to boot in secure mode, which isn't
right for AArch64 Linux kernels
* the hw/arm/boot.c code didn't set SCR_EL3.HCE, which meant that
Now we have separate types for BCM2386 and BCM2387, we might as well
just hard-code the CPU type they use rather than having it passed
through as an object property. This then lets us put the initialization
of the CPU object in init rather than realize.
Signed-off-by: Peter Maydell
Add some assertions that if we're about to boot an AArch64 kernel,
the board code has not mistakenly set either secure_boot or
secure_board_setup. It doesn't make sense to set secure_boot,
because all AArch64 kernels must be booted in non-secure mode.
It might in theory make sense to set
On 03/12/2018 10:21 AM, Vladimir Sementsov-Ogievskiy wrote:
Minimal realization: only one extent in server answer is supported.
Flag NBD_CMD_FLAG_REQ_ONE is used to force this behavior.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
v2: - drop iotests changes, as
The BCM2837 sets the Aff1 field of the MPIDR affinity values for the
CPUs to 0, whereas the BCM2836 uses 0xf. Set this correctly, as it
is required for Linux to boot.
Signed-off-by: Peter Maydell
---
hw/arm/bcm2836.c | 7 ++-
1 file changed, 6 insertions(+), 1
For the rpi1 and 2 we want to boot the Linux kernel via some
custom setup code that makes sure that the SMC instruction
acts as a no-op, because it's used for cache maintenance.
The rpi3 boots AArch64 kernels, which don't need SMC for
cache maintenance and always expect to be booted non-secure.
If we're directly booting a Linux kernel and the CPU supports both
EL3 and EL2, we start the kernel in EL2, as it expects. We must also
set the SCR_EL3.HCE bit in this situation, so that the HVC
instruction is enabled rather than UNDEFing. Otherwise at least some
kernels will panic when trying to
The TypeInfo and state struct for bcm2386 disagree about what the
parent class is -- the TypeInfo says it's TYPE_SYS_BUS_DEVICE,
but the BCM2386State struct only defines the parent_obj field
as DeviceState. This would have caused problems if anything
actually tried to treat the object as a
On Tue, Mar 13, 2018 at 03:32:08PM +, Alex Bennée wrote:
> As the build times have risen we keep timing out. Split the default
> config into system and user builds.
>
> Signed-off-by: Alex Bennée
> ---
> .travis.yml | 3 ++-
> 1 file changed, 2 insertions(+), 1
The raspi3 has AArch64 CPUs, which means that our smpboot
code for keeping the secondary CPUs in a pen needs to have
a version for A64 as well as A32. Without this, the
secondary CPUs go into an infinite loop of taking undefined
instruction exceptions.
Signed-off-by: Peter Maydell
The log backend is the default one, we don't need to explicitly set it.
Signed-off-by: Alex Bennée
---
.travis.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.travis.yml b/.travis.yml
index 79377c8de0..92c343a1ef 100644
--- a/.travis.yml
+++
On Tue, Mar 13, 2018 at 03:32:07PM +, Alex Bennée wrote:
> The log backend is the default one, we don't need to explicitly set it.
>
> Signed-off-by: Alex Bennée
> ---
> .travis.yml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/.travis.yml
On Tue, Mar 13, 2018 at 03:32:09PM +, Alex Bennée wrote:
> As all the disabled features only affect system emulation we might as
> well disable user mode to save compile time.
>
> Signed-off-by: Alex Bennée
> ---
> .travis.yml | 2 +-
> 1 file changed, 1
As the build times have risen we keep timing out. Split the default
config into system and user builds.
Signed-off-by: Alex Bennée
---
.travis.yml | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/.travis.yml b/.travis.yml
index 92c343a1ef..75e5b408d0
The tools are already built elsewhere so we might as well not build it
here as we just need to test the modules build of QEMU itself.
Signed-off-by: Alex Bennée
---
.travis.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.travis.yml b/.travis.yml
As all the disabled features only affect system emulation we might as
well disable user mode to save compile time.
Signed-off-by: Alex Bennée
---
.travis.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.travis.yml b/.travis.yml
index
Hi,
As QEMU has grown it has started to hit the Travis timeouts a lot
more. These patches try and address that by selectively adding
--disable-user and --disable-system to the place (and adding a new
matrix entry).
: patch 0001/.travis.yml drop setting default log output.patch needs review
:
On 12 March 2018 at 20:00, Eduardo Habkost wrote:
> The following changes since commit b16a54da0696efc5d91b6c3597a37a317abb5de7:
>
> Merge remote-tracking branch 'remotes/kraxel/tags/ui-20180312-pull-request'
> into staging (2018-03-12 14:06:23 +)
>
> are available in
On Mon, Mar 12, 2018 at 1:21 PM, Greg Kurz wrote:
> On Mon, 12 Mar 2018 13:08:29 +
> Daniel P. Berrangé wrote:
>
>> On Mon, Mar 12, 2018 at 02:02:29PM +0100, Greg Kurz wrote:
>> > On Mon, 12 Mar 2018 07:12:52 -0500
>> > Eric Blake
301 - 400 of 556 matches
Mail list logo