commit_msg
stringlengths 1
24.2k
| commit_hash
stringlengths 2
84
⌀ | project
stringlengths 2
40
| source
stringclasses 4
values | labels
int64 0
1
| repo_url
stringlengths 26
70
⌀ | commit_url
stringlengths 74
118
⌀ | commit_date
stringlengths 25
25
⌀ |
|---|---|---|---|---|---|---|---|
kvm: Relax aligment check of kvm_set_phys_mem
There is no need to reject an unaligned memory region registration if
the region will be I/O memory and it will not split an existing KVM
slot. This fixes KVM support on PPC.
Signed-off-by: Jan Kiszka <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
e6f4afe029ae21853fd6625d94e9e0b2caa4defd
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/e6f4afe029ae21853fd6625d94e9e0b2caa4defd
|
2009-05-01 09:38:33-05:00
|
block-raw: Allow pread beyond the end of growable images
When using O_DIRECT, qcow2 snapshots didn't work any more for me. In the
process of creating the snapshot, qcow2 tries to pwrite some new information
(e.g. new L1 table) which will often end up being after the old end of the
image file. Now pwrite tries to align things and reads the old contents of the
file, read returns 0 because there is nothing to read after the end of file and
pwrite is stuck in an endless loop.
This patch allows to pread beyond the end of an image file. Whenever the
given offset is after the end of the image file, the read succeeds and fills
the buffer with zeros.
Signed-off-by: Kevin Wolf <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
22afa7b5b67bb8bc58939d100363ee6753a50467
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/22afa7b5b67bb8bc58939d100363ee6753a50467
|
2009-06-29 14:18:07-05:00
|
net: Fix -net socket parameter checks
My commit ea053add700d8abe203cd79a9ffb082aee4eabc0 broke -net socket by
overwriting an intermediate buffer in the added check_param. Fix this
by switching check_param to automatic buffer allocation and release, ie.
callers no longer have to worry about providing a scratch buffer.
Signed-off-by: Jan Kiszka <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
ffad4116b96e29e0fbe892806f97c0a6c903d30d
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/ffad4116b96e29e0fbe892806f97c0a6c903d30d
|
2009-05-01 09:44:11-05:00
|
Use a dedicated function to request exit from execution loop
Signed-off-by: Aurelien Jarno <[email protected]>
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6762 c046a42c-6fe2-441c-8c8c-71466251a162
|
3098dba01c7daab60762b6f6624ea88c0d6cb65a
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/3098dba01c7daab60762b6f6624ea88c0d6cb65a
|
2009-03-07 21:28:24+00:00
|
Introduce bdrv_check (Kevin Wolf)
From: Kevin Wolf <[email protected]>
Introduce a new bdrv_check function pointer for block drivers. Modify qcow2 to
return an error status in check_refcounts(), so it can implement bdrv_check.
Signed-off-by: Kevin Wolf <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@7214 c046a42c-6fe2-441c-8c8c-71466251a162
|
e97fc193e1c65deb51643d5251e98affe07c59ca
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/e97fc193e1c65deb51643d5251e98affe07c59ca
|
2009-04-21 23:11:50+00:00
|
monitor: Rework modal password input (Jan Kiszka)
Currently, waiting for the user to type in some password blocks the
whole VM because monitor_readline starts its own I/O loop. And this loop
also screws up reading passwords from virtual console.
Patch below fixes the shortcomings by using normal I/O processing also
for waiting on a password. To keep to modal property for the monitor
terminal, the command handler is temporarily replaced by a password
handler and a callback infrastructure is established to process the
result before switching back to command mode.
Signed-off-by: Jan Kiszka <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6710 c046a42c-6fe2-441c-8c8c-71466251a162
|
bb5fc20f7c1c65e95030da3629dd0d7a0cce38cd
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/bb5fc20f7c1c65e95030da3629dd0d7a0cce38cd
|
2009-03-05 23:01:15+00:00
|
Remove useless check_ops.sh
Suggested by Stuart Brady.
Signed-off-by: Aurelien Jarno <[email protected]>
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5999 c046a42c-6fe2-441c-8c8c-71466251a162
|
8d32699adeb10f9255a5ad7229c2d3aa7a726b5a
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/8d32699adeb10f9255a5ad7229c2d3aa7a726b5a
|
2008-12-13 09:03:28+00:00
|
Fix tap downscript argument (Mark McLoughlin)
Kill off the hack that parses info_str for the tap interface
name to pass as the argument to the downscript and, instead,
just explicitly keep a copy of the string for later.
As reported by John Wong, this commit:
Add qemu_format_nic_info_str()
changed the invocation of downscript from e.g.
/path/kvm-ifdown "tap0"
to:
/path/kvm-ifdown "tap0,script=/path/kvm-ifup,downscript=/path/kvm-ifdown"
This fix restores the original behavior.
Reported-by: John Wong <[email protected]>
Signed-off-by: Mark McLoughlin <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6285 c046a42c-6fe2-441c-8c8c-71466251a162
|
973cbd37ce6d4c33dea7f4ed6b8e0e602fa50d25
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/973cbd37ce6d4c33dea7f4ed6b8e0e602fa50d25
|
2009-01-13 19:15:55+00:00
|
Parse --cc and --cross-prefix earlier and use CC to determine cpu and host
We have been relying on uname to determine the host cpu architecture and
operating system. This is totally broken for cross compilation. It was
workable in the past because you can manually override both settings but after
the host USB passthrough refactoring, cross host builds were broken.
This moves the parsing of --cc and --cross-prefix to before the probes for cpu
and host. Complation testing is used to determine the host and CPU types. I've
only added checks for i386, x86_64, Linux, and Windows since these are the only
platforms I have access to for testing. Everything else falls back to uname.
It should be relatively easy to add the right checks for other platforms and
eliminate uname altogether.
Signed-off-by: Anthony Liguori <[email protected]>
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6141 c046a42c-6fe2-441c-8c8c-71466251a162
|
ac0df51d7b3e0a76923a03efa2cfdec4b9f65ef5
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/ac0df51d7b3e0a76923a03efa2cfdec4b9f65ef5
|
2008-12-29 17:14:15+00:00
|
target-mips: gen_compute_branch1()
Optimize code generation in gen_compute_branch1():
- Directly use I32 variables instead of converting values from _tl to
_i32 and back to _tl.
- Write the result directly to bcond instead of passing by a local
variable.
- Temp variables are valid up to and *including* the brcond instruction.
Use them instead of temp local variables.
Signed-off-by: Aurelien Jarno <[email protected]>
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5684 c046a42c-6fe2-441c-8c8c-71466251a162
|
a6e92a658b99b4ab3b19b2f32352005e6190556f
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/a6e92a658b99b4ab3b19b2f32352005e6190556f
|
2008-11-11 11:50:51+00:00
|
linux-user: Fix h2g usage in page_find_alloc
Paul's comment on my first approach to fix the h2g usage in
page_find_alloc finally open my eyes about what the code is actually
supposed to do:
With the help of h2g_valid we can no cleanly check if a freshly allocate
page (for host usage) is guest-reachable and, in case it is, mark it
reserved in the guest's address range.
Signed-off-by: Jan Kiszka <[email protected]>
Signed-off-by: Kirill A. Shutemov <[email protected]>
Acked-by: Edgar E. Iglesias <[email protected]>
Signed-off-by: Aurelien Jarno <[email protected]>
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5957 c046a42c-6fe2-441c-8c8c-71466251a162
|
fb1c2cd7d9a9955a98eb7c874a74122f1e964811
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/fb1c2cd7d9a9955a98eb7c874a74122f1e964811
|
2008-12-08 18:12:26+00:00
|
Switch the memory savevm handler to be "live"
This patch replaces the static memory savevm/loadvm handler with a "live" one.
This handler is used even if performing a non-live migration.
The key difference between this handler and the previous is that each page is
prefixed with the address of the page. The QEMUFile rate limiting code, in
combination with the live migration dirty tracking bits, is used to determine
which pages should be sent and how many should be sent.
The live save code "converges" when the number of dirty pages reaches a fixed
amount. Currently, this is 10 pages. This is something that should eventually
be derived from whatever the bandwidth limitation is.
Signed-off-by: Anthony Liguori <[email protected]>
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5437 c046a42c-6fe2-441c-8c8c-71466251a162
|
475e4277721eca10e98bd926fa1d3ebc74d0ac35
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/475e4277721eca10e98bd926fa1d3ebc74d0ac35
|
2008-10-06 20:21:51+00:00
|
Disable OMAP2 combined-io-entries hack now that more regions are allowed.
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@4879 c046a42c-6fe2-441c-8c8c-71466251a162
|
477b24ef911753e1debbacf798242a06de0af96c
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/477b24ef911753e1debbacf798242a06de0af96c
|
2008-07-16 13:06:53+00:00
|
IDE SEEK_STAT flag
Add SEEK_STAT in all non-error cases except sleep request, since our
seek times are virtually 0. Although this flag is deprecated by newer
ATA standards, Linux at least checks it for CD drives, and would timeout
in some case if we do not set it.
Signed-off-by: Samuel Thibault <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@4994 c046a42c-6fe2-441c-8c8c-71466251a162
|
41a2b9596c9ed2a827e16e749632752dd2686647
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/41a2b9596c9ed2a827e16e749632752dd2686647
|
2008-08-11 18:52:14+00:00
|
Fix MusicPal LCD on non-32 bpp displays or with -nographic.
Prevents an immediate segfault.
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@4252 c046a42c-6fe2-441c-8c8c-71466251a162
|
0266f2c733911ca3f70e009e3230c790c800e524
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/0266f2c733911ca3f70e009e3230c790c800e524
|
2008-04-25 00:59:43+00:00
|
Increase max temps limit
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@4074 c046a42c-6fe2-441c-8c8c-71466251a162
|
c4071c90143c6c356ad670e6ed03024b14ce4fa7
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/c4071c90143c6c356ad670e6ed03024b14ce4fa7
|
2008-03-16 19:21:07+00:00
|
Check for 3DNow! CPUID at translation time
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@4184 c046a42c-6fe2-441c-8c8c-71466251a162
|
e771edab0d9aaa7925dc26aec3e0c6eac27f19c3
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/e771edab0d9aaa7925dc26aec3e0c6eac27f19c3
|
2008-04-09 06:41:37+00:00
|
Enable all alignment checks
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@3404 c046a42c-6fe2-441c-8c8c-71466251a162
|
8f577d3d29996ad5c60ac6419881557183806d8b
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/8f577d3d29996ad5c60ac6419881557183806d8b
|
2007-10-17 17:34:57+00:00
|
Fix usermode check, thanks Aurelien Jarno.
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@2897 c046a42c-6fe2-441c-8c8c-71466251a162
|
78749ba859684748366b5de630ad41bd1b2d60a2
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/78749ba859684748366b5de630ad41bd1b2d60a2
|
2007-05-29 18:55:34+00:00
|
Check permissions for the last byte first in unaligned slow_st accesses (patch from TeLeMan).
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@3665 c046a42c-6fe2-441c-8c8c-71466251a162
|
7221fa98d381a19b8809979934554644381fb88c
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/7221fa98d381a19b8809979934554644381fb88c
|
2007-11-17 09:53:42+00:00
|
prevent window resizing
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@1519 c046a42c-6fe2-441c-8c8c-71466251a162
|
1ff5c1a68e2784722b66ecc40e30908e87e28a3b
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/1ff5c1a68e2784722b66ecc40e30908e87e28a3b
|
2005-07-23 17:54:50+00:00
|
Test if compiler works instead of checking if binary exists.
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@1909 c046a42c-6fe2-441c-8c8c-71466251a162
|
064aae138b1b26d326603c5c46763e6bde4bf5f2
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/064aae138b1b26d326603c5c46763e6bde4bf5f2
|
2006-05-08 00:51:44+00:00
|
Initialize physical memory space to IO_MEM_UNASSIGNED.
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@1801 c046a42c-6fe2-441c-8c8c-71466251a162
|
e3f4e2a4b0df510e441badb85c9398516c27bd66
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/e3f4e2a4b0df510e441badb85c9398516c27bd66
|
2006-04-08 20:02:06+00:00
|
suppressed ppc ide hack - fixed read toc for Darwin/PPC
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@1509 c046a42c-6fe2-441c-8c8c-71466251a162
|
a368741bf2508b7ca29d9ade73ec1b0f29ae2286
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/a368741bf2508b7ca29d9ade73ec1b0f29ae2286
|
2005-07-07 21:46:09+00:00
|
Throw RI for invalid MFMC0-class instructions. Introduce optional
MIPS_STRICT_STANDARD define to adhere more to the spec than it makes
sense in normal operation.
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@2650 c046a42c-6fe2-441c-8c8c-71466251a162
|
b48cfdffd9f15432355c8e4ed9d2781eab9e4358
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/b48cfdffd9f15432355c8e4ed9d2781eab9e4358
|
2007-04-11 02:24:14+00:00
|
Windows 2000 install disk full hack (original idea from Vladimir N. Oleynik)
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@1428 c046a42c-6fe2-441c-8c8c-71466251a162
|
a09db21f711237d01375b64e6a4da676e88d4f37
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/a09db21f711237d01375b64e6a4da676e88d4f37
|
2005-04-30 16:10:35+00:00
|
temporary hack for PowerPC system emulation
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@436 c046a42c-6fe2-441c-8c8c-71466251a162
|
c970a162e7b152622b394f9268fc4aeb0f0e3b20
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/c970a162e7b152622b394f9268fc4aeb0f0e3b20
|
2003-10-30 01:21:44+00:00
|
separated readline from monitor code - added password input support - added output buffer
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@1034 c046a42c-6fe2-441c-8c8c-71466251a162
|
7e2515e87c41e2e658aaed466e11cbdf1ea8bcb1
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/7e2515e87c41e2e658aaed466e11cbdf1ea8bcb1
|
2004-08-01 21:52:19+00:00
|
fixed invalid CPL logic in vm86 mode - use generic CPU dump state function
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@142 c046a42c-6fe2-441c-8c8c-71466251a162
|
9d27abd94fe2c48281a77112d58422b392a80f7b
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/9d27abd94fe2c48281a77112d58422b392a80f7b
|
2003-05-10 13:13:54+00:00
|
s390x/tcg: implement TEST PROTECTION
Linux uses TEST PROTECTION to sense for available memory locations.
Let's implement what we can for now (just as for the other instructions,
excluding AR mode and special protection mechanisms).
Signed-off-by: David Hildenbrand <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Thomas Huth <[email protected]>
Signed-off-by: Cornelia Huck <[email protected]>
|
bb8794307252be791f1723eae47983f815882376
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/bb8794307252be791f1723eae47983f815882376
|
2018-01-22 11:04:52+01:00
|
tests/cpu-plug-test: Check CPU hot-plugging on ppc64, too
Hot plugging on ppc64 is possible via "device_add", too. Unlike x86,
we must not specify a 'socket-id' and 'thread-id' here, so this needs
to be done with a separate function that just specifies the 'core-id'
during the "device_add".
Reviewed-by: Daniel Barboza <[email protected]>
Tested-by: Daniel Barboza <[email protected]>
Signed-off-by: Thomas Huth <[email protected]>
|
73a7d31e53e2b34f83b5e138189b9bab1333f3b9
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/73a7d31e53e2b34f83b5e138189b9bab1333f3b9
|
2018-01-22 08:39:05+01:00
|
icount: fixed saving/restoring of icount warp timers
This patch adds saving and restoring of the icount warp
timers in the vmstate.
It is needed because there timers affect the virtual clock value.
Therefore determinism of the execution in icount record/replay mode
depends on determinism of the timers.
Signed-off-by: Pavel Dovgalyuk <[email protected]>
Acked-by: Paolo Bonzini <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Signed-off-by: Pavel Dovgalyuk <[email protected]>
|
b39e3f34c9de7ead6a11a74aa2de78baf41d81a7
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/b39e3f34c9de7ead6a11a74aa2de78baf41d81a7
|
2018-01-16 14:54:51+01:00
|
i386: hvf: implement vga dirty page tracking
This patch implements setting the tracking of dirty vga pages, using hvf's
interface to protect guest memory. It uses the MemoryListener callback
mechanism through .log_start/stop/sync
Signed-off-by: Sergio Andres Gomez Del Real <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
|
babfa20ca4721e950d8096f32b1dc091763a8837
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/babfa20ca4721e950d8096f32b1dc091763a8837
|
2017-12-22 15:01:48+01:00
|
s390x/pci: rework PCI STORE BLOCK
Enhance the fault detection.
Fixup the precedence to check the destination path existance
before checking for the source accessibility.
Add the maxstbl entry to both the Query PCI Function Group
response and the PCIBusDevice structure.
Initialize the maxstbl to 128 per default until we get
the actual data from the hardware.
Signed-off-by: Pierre Morel <[email protected]>
Reviewed-by: Yi Min Zhao <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Cornelia Huck <[email protected]>
|
0e7c259adff7e97f829a08a5f146e7ee03b5ae47
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/0e7c259adff7e97f829a08a5f146e7ee03b5ae47
|
2017-12-14 17:56:54+01:00
|
blockdev: add x-blockdev-set-iothread force boolean
When a node is already associated with a BlockBackend the
x-blockdev-set-iothread command refuses to set the IOThread. This is to
prevent accidentally changing the IOThread when the nodes are in use.
When the nodes are created with -drive they automatically get a
BlockBackend. In that case we know nothing is using them yet and it's
safe to set the IOThread. Add a force boolean to override the check.
Signed-off-by: Stefan Hajnoczi <[email protected]>
Reviewed-by: Eric Blake <[email protected]>
Message-id: [email protected]
Signed-off-by: Stefan Hajnoczi <[email protected]>
|
882e9b89af7c1086d97cee11b2437337e756fa00
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/882e9b89af7c1086d97cee11b2437337e756fa00
|
2017-12-19 10:25:09+00:00
|
s390x/tcg: don't exit the cpu loop in s390_cpu_virt_mem_rw()
s390_cpu_virt_mem_rw() must always return, so callers can react on
an exception (e.g. see ioinst_handle_stcrw()).
Therefore, using program_interrupt() is wrong. Fix that up.
Signed-off-by: David Hildenbrand <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Cornelia Huck <[email protected]>
|
820613b1c1c76cb77a15313eb333a710972614ec
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/820613b1c1c76cb77a15313eb333a710972614ec
|
2017-12-14 17:56:54+01:00
|
target/arm: Implement TT instruction
Implement the TT instruction which queries the security
state and access permissions of a memory location.
Signed-off-by: Peter Maydell <[email protected]>
Reviewed-by: Richard Henderson <[email protected]>
Message-id: [email protected]
|
5158de241b0fb344a6c948dfcbc4e611ab5fafbe
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/5158de241b0fb344a6c948dfcbc4e611ab5fafbe
|
2017-12-13 17:59:24+00:00
|
target/arm: Handle SPSEL and current stack being out of sync in MSP/PSP reads
For v8M it is possible for the CONTROL.SPSEL bit value and the
current stack to be out of sync. This means we need to update
the checks used in reads and writes of the PSP and MSP special
registers to use v7m_using_psp() rather than directly checking
the SPSEL bit in the control register.
Signed-off-by: Peter Maydell <[email protected]>
Reviewed-by: Richard Henderson <[email protected]>
Message-id: [email protected]
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
|
1169d3aa5b19adca9384d954d80e1f48da388284
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/1169d3aa5b19adca9384d954d80e1f48da388284
|
2017-12-13 17:59:23+00:00
|
9pfs: fix v9fs_mark_fids_unreclaim() return value
The return value of v9fs_mark_fids_unreclaim() is then propagated to
pdu_complete(). It should be a negative errno, not -1.
Signed-off-by: Greg Kurz <[email protected]>
Reviewed-by: Eric Blake <[email protected]>
|
267fcadf325e54c6e1cb27321413dbdbe2200510
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/267fcadf325e54c6e1cb27321413dbdbe2200510
|
2017-11-06 18:05:35+01:00
|
block: Don't request I/O permission with BDRV_O_NO_IO
'qemu-img info' makes sense even when BLK_PERM_CONSISTENT_READ cannot be
granted because of a block job in a running qemu process. It already
sets BDRV_O_NO_IO to indicate that it doesn't access the guest visible
data at all.
Check the BDRV_O_NO_IO flags in blk_new_open(), so that I/O related
permissions are not unnecessarily requested and 'qemu-img info' can work
even if BLK_PERM_CONSISTENT_READ cannot be granted.
Signed-off-by: Kevin Wolf <[email protected]>
Reviewed-by: Fam Zheng <[email protected]>
Reviewed-by: Alberto Garcia <[email protected]>
|
1f4ad7d3b8f7162ec0471506d86f57a5d77b8f76
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/1f4ad7d3b8f7162ec0471506d86f57a5d77b8f76
|
2017-11-21 14:48:22+01:00
|
disas: Add capstone as submodule
Do not require the submodule, but use it if present. Allow the
command-line to override system or git submodule either way.
Tested-by: Philippe Mathieu-Daudé <[email protected]>
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
Signed-off-by: Richard Henderson <[email protected]>
|
e219c499e9f5d4fa0e25dc07682f75531ee84d86
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/e219c499e9f5d4fa0e25dc07682f75531ee84d86
|
2017-10-26 11:56:20+02:00
|
qga-win: Updating guest_set_time action
At the moment, Windows libraries don't provide a way to access
RTC, so, a workaround is to use the Windows w32tm command to
resync the time.
Related bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1183874
Signed-off-by: Bishara AbuHattoum <[email protected]>
Reviewed-by: Sameeh Jubran <[email protected]>
Signed-off-by: Michael Roth <[email protected]>
|
105fad6bb226ac3404874fe3fd7013ad6f86fc86
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/105fad6bb226ac3404874fe3fd7013ad6f86fc86
|
2017-10-25 17:50:50-05:00
|
cpu-exec: avoid cpu_exec_nocache infinite loop with record/replay
This patch ensures that icount_decr.u32.high is clear before calling
cpu_exec_nocache when exception is pending. Because the exception is
caused by the first instruction in the block and it cannot be executed
without resetting the flag.
There are two parts in the fix. First, clear icount_decr.u32.high in
cpu_handle_interrupt (just before processing the "dependent" request,
stored in cpu->interrupt_request or cpu->exit_request) rather than
cpu_loop_exec_tb; this ensures that cpu_handle_exception is always
reached with zero icount_decr.u32.high unless another interrupt has
happened in the meanwhile.
Second, try to cause the exception at the beginning of
cpu_handle_exception, and exit immediately if the TB cannot
execute. With this change, interrupts are processed and
cpu_exec_nocache can make process.
Signed-off-by: Maria Klimushenkova <[email protected]>
Signed-off-by: Pavel Dovgalyuk <[email protected]>
Message-Id: <20171114081818.27640.33165.stgit@pasha-VirtualBox>
Signed-off-by: Paolo Bonzini <[email protected]>
|
17b50b0c299f1266578b01f7134810362418ac2e
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/17b50b0c299f1266578b01f7134810362418ac2e
|
2017-11-14 14:46:46+01:00
|
tpm-emulator: fix error handling
The previous patch cleaned up a bit error handling, and exposed an
existing bug: error_report_err() could be called with a NULL error.
Instead, make tpm_emulator_set_locality() set the error.
Signed-off-by: Marc-André Lureau <[email protected]>
Reviewed-by: Stefan Berger <[email protected]>
Signed-off-by: Stefan Berger <[email protected]>
|
c106ede9c85bf4b38c52dbee96b00c2aa0a97dee
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/c106ede9c85bf4b38c52dbee96b00c2aa0a97dee
|
2017-10-19 11:42:28-04:00
|
linux-user: Allow -R values up to 0xffff0000 for 32-bit ARM guests
The 32-bit ARM validate_guest_space() check tests whether the
specified -R value leaves enough space for us to put the
commpage in at 0xffff0f00. However it was incorrectly doing
a <= check for the check against (guest_base + guest_size),
which meant that it wasn't permitting the guest space to
butt right up against the commpage.
Fix the comparison, so that -R values all the way up to 0xffff0000
work correctly.
Reviewed-by: Emilio G. Cota <[email protected]>
Signed-off-by: Peter Maydell <[email protected]>
Signed-off-by: Riku Voipio <[email protected]>
|
e568f9df086965813a318ff0558782ba90e59c33
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/e568f9df086965813a318ff0558782ba90e59c33
|
2017-10-16 16:00:56+03:00
|
block/nbd-client: assert qiov len once in nbd_co_request
Also improve the assertion: check that qiov is NULL for other commands
than CMD_READ and CMD_WRITE.
Signed-off-by: Vladimir Sementsov-Ogievskiy <[email protected]>
Reviewed-by: Eric Blake <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Eric Blake <[email protected]>
|
4bfe4478d17679464a2aaa91ed703522ed9af8a0
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/4bfe4478d17679464a2aaa91ed703522ed9af8a0
|
2017-10-12 16:19:35-05:00
|
block/nbd-client: simplify check in nbd_co_receive_reply
If we are woken up from while() loop in nbd_read_reply_entry
handles must be equal. If we are woken up from
nbd_recv_coroutines_wake_all s->quit must be true, so we do
not need checking handles equality.
Signed-off-by: Vladimir Sementsov-Ogievskiy <[email protected]>
Reviewed-by: Eric Blake <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Eric Blake <[email protected]>
|
93970672210ca1ee45fdebbc11e1fd97916c7c8e
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/93970672210ca1ee45fdebbc11e1fd97916c7c8e
|
2017-09-25 08:21:26-05:00
|
watchdog: Allow setting action on the fly
Currently, the only time that users can set watchdog action is at
the start as all we expose is this -watchdog-action command line
argument. This is suboptimal when users want to plug the device
later via monitor. Alternatively, they might want to change the
action for already existing device on the fly.
Inspired by: https://bugzilla.redhat.com/show_bug.cgi?id=1447169
Signed-off-by: Michal Privoznik <[email protected]>
Message-Id: <35d6ce6fe3d357122d73b8272bc8198134c74104.1504771369.git.mprivozn@redhat.com>
Reviewed-by: Eric Blake <[email protected]>
Reviewed-by: Markus Armbruster <[email protected]>
Reviewed-by: Daniel P. Berrange <[email protected]>
[Missing colon in doc comment fixed]
Signed-off-by: Markus Armbruster <[email protected]>
|
f0df84c6c46cb632dac2d9fae5fdbe6001527c3b
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/f0df84c6c46cb632dac2d9fae5fdbe6001527c3b
|
2017-10-02 13:09:09+02:00
|
tests: Enable the drive_del test also on s390x
We can use the drive_del test on s390x, too, to check that adding and
deleting also works fine with the virtio-ccw bus. But we have to make
sure that we use the devices with the "-ccw" suffix instead of the
"-pci" suffix for the virtio-ccw transport on s390x. Introduce a helper
function called qvirtio_get_dev_type() that returns the correct string
for the current architecture.
Signed-off-by: Thomas Huth <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: David Hildenbrand <[email protected]>
Signed-off-by: Cornelia Huck <[email protected]>
|
2f84a92ec631f5907207990705a22afb9aad3eef
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/2f84a92ec631f5907207990705a22afb9aad3eef
|
2017-09-19 18:21:32+02:00
|
target/arm: Make MPU_RNR register banked for v8M
Make the MPU_RNR register banked if v8M security extensions are
enabled.
Signed-off-by: Peter Maydell <[email protected]>
Reviewed-by: Richard Henderson <[email protected]>
Message-id: [email protected]
|
1bc04a8880374407c4b12d82ceb8752e12ff5336
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/1bc04a8880374407c4b12d82ceb8752e12ff5336
|
2017-09-07 13:54:53+01:00
|
vfio, spapr: Fix levels calculation
The existing tries to round up the number of pages but @pages is always
calculated as the rounded up value minus one which makes ctz64() always
return 0 and have create.levels always set 1.
This removes wrong "-1" and allows having more than 1 levels. This becomes
handy for >128GB guests with standard 64K pages as this requires blocks
with zone order 9 and the popular limit of CONFIG_FORCE_MAX_ZONEORDER=9
means that only blocks up to order 8 are allowed.
Signed-off-by: Alexey Kardashevskiy <[email protected]>
Signed-off-by: David Gibson <[email protected]>
|
e100161b69f8cf56dae866912dfffe7dcd7140af
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/e100161b69f8cf56dae866912dfffe7dcd7140af
|
2017-09-15 10:29:48+10:00
|
tcg/s390: Merge cmpi facilities check to tcg_target_op_def
Acked-by: Cornelia Huck <[email protected]>
Signed-off-by: Richard Henderson <[email protected]>
|
07952d9570add4c78594b46605825408d956b2ad
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/07952d9570add4c78594b46605825408d956b2ad
|
2017-09-06 07:24:28-07:00
|
target/arm: [tcg] Port to disas_log
Incrementally paves the way towards using the generic instruction translation
loop.
Signed-off-by: Lluís Vilanova <[email protected]>
Reviewed-by: Richard Henderson <[email protected]>
Reviewed-by: Alex Benneé <[email protected]>
Message-Id: <[email protected]>
[rth: Move tb->size computation and use that result.]
Signed-off-by: Richard Henderson <[email protected]>
|
4013f7fc811e90b89da3a516dc71b01ca0e7e54e
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/4013f7fc811e90b89da3a516dc71b01ca0e7e54e
|
2017-09-06 08:06:48-07:00
|
sun4u: expose fw_cfg and NVRAM on ebus PCI IO address space
To allow future changes to the sun4u PCI topology.
Signed-off-by: Mark Cave-Ayland <[email protected]>
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
Acked-By: Artyom Tarasenko <[email protected]>
|
07c847413b8e3776f2f2c4375b2838d4ee0008ed
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/07c847413b8e3776f2f2c4375b2838d4ee0008ed
|
2017-09-04 18:41:01+01:00
|
tests/pxe: Check virtio-net-ccw on s390x
Now that we've got a firmware that can do TFTP booting on s390x (i.e.
the pc-bios/s390-netboot.img), we can enable the PXE tester for this
architecture, too.
Signed-off-by: Thomas Huth <[email protected]>
Reviewed-by: Cornelia Huck <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Cornelia Huck <[email protected]>
|
b1b2feac9432869a129b5958cd697d2870ffcc6b
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/b1b2feac9432869a129b5958cd697d2870ffcc6b
|
2017-08-30 18:23:25+02:00
|
loader: Ignore zero-sized ELF segments
Some ELF files have program headers that specify segments that
are of zero size. Ignore them, rather than trying to create
zero-length ROM blobs for them, because the zero-length blob
can falsely trigger the overlapping-ROM-blobs check.
Signed-off-by: Peter Maydell <[email protected]>
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
Reviewed-by: Richard Henderson <[email protected]>
Tested-by: Hua Yanghao <[email protected]>
Message-id: [email protected]
|
f33e5e6299288c945380e3ce3ea9d2406277c289
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/f33e5e6299288c945380e3ce3ea9d2406277c289
|
2017-09-04 15:21:53+01:00
|
sparc: move adhoc CPUSPARCState initialization to realize time
SPARCCPU::env was initialized from previously set properties
(with help of sparc_cpu_parse_features) in cpu_sparc_register().
However there is not reason to keep it there as this task is
typically done at realize time. So move post properties
initialization into sparc_cpu_realizefn, which brings
cpu_sparc_init() closer to cpu_generic_init().
Signed-off-by: Igor Mammedov <[email protected]>
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
Tested-by: Philippe Mathieu-Daudé <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Eduardo Habkost <[email protected]>
|
700549620b3ee15924f19b9eb79961655ce671c5
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/700549620b3ee15924f19b9eb79961655ce671c5
|
2017-09-01 11:54:24-03:00
|
migration: optimize the downtime
Qemu_savevm_state_cleanup takes about 300ms in my ram migration tests
with a 8U24G vm(20G is really occupied), the main cost comes from
KVM_SET_USER_MEMORY_REGION ioctl when mem.memory_size = 0 in
kvm_set_user_memory_region. In kmod, the main cost is
kvm_zap_obsolete_pages, which traverses the active_mmu_pages list to
zap the unsync sptes.
It can be optimized by delaying memory_global_dirty_log_stop to the next
vm_start.
Changes v2->v3:
- NULL VMChangeStateHandler if it is deleted and protect the scenario
of nested invocations of memory_global_dirty_log_start/stop [Paolo]
Changes v1->v2:
- create a VMChangeStateHandler in memory.c to reduce the coupling [Paolo]
Signed-off-by: Jay Zhou <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
|
1931076077254a2886daa7c830c7838ebd1f81ef
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/1931076077254a2886daa7c830c7838ebd1f81ef
|
2017-08-01 17:27:33+02:00
|
s390x/css: generate solicited crw for rchp completion signaling
A successful completion of rchp should signal a solicited channel path
initialized CRW (channel report word), while the current implementation
always generates an un-solicited one. Let's fix this.
Reported-by: Halil Pasic <[email protected]>
Signed-off-by: Dong Jia Shi <[email protected]>
Reviewed-by: Halil Pasic <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Cornelia Huck <[email protected]>
|
5c8d6f008c0555b54cf10550fa86199a2cfabbca
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/5c8d6f008c0555b54cf10550fa86199a2cfabbca
|
2017-08-30 18:23:25+02:00
|
libqtest: always set up signal handler for SIGABRT
Currently abort handlers only work for the first test function
in a testcase, because the list of abort handlers is not properly
cleared when qtest_quit() is called.
qtest_quit() only deletes the kill_qemu_hook but doesn't completely
clear the abrt_hooks list. The effect is that abrt_hooks.is_setup is
never set to false and in a following test the abrt_hooks list is not
initialized and setup_sigabrt_handler() is not called.
One way to solve this is to clear the list in qtest_quit(), but
that means only asserts between qtest_start and qtest_quit will
be catched by the abort handler.
We can make abort handlers work in all cases if we always setup the
signal handler for SIGABRT in qtest_init.
Signed-off-by: Jens Freimann <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
|
24dd1e17696fbd11b3df50718dddcbdfe2c45f24
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/24dd1e17696fbd11b3df50718dddcbdfe2c45f24
|
2017-08-09 04:22:14+03:00
|
target/mips: Weaken TLB flush on UX,SX,KX,ASID changes
There is no need to invalidate any shadow TLB entries when the ASID
changes or when access to one of the 64-bit segments has been disabled,
since doing so doesn't reveal to software whether any TLB entries have
been evicted into the shadow half of the TLB.
Therefore weaken the tlb flushes in these cases to only flush the QEMU
TLB.
Signed-off-by: James Hogan <[email protected]>
Cc: Yongbok Kim <[email protected]>
Cc: Aurelien Jarno <[email protected]>
Tested-by: Yongbok Kim <[email protected]>
Signed-off-by: Yongbok Kim <[email protected]>
|
9658e4c342e6ae0d775101f8f6bb6efb16789af1
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/9658e4c342e6ae0d775101f8f6bb6efb16789af1
|
2017-07-20 22:42:26+01:00
|
slirp: use DIV_ROUND_UP
I used the clang-tidy qemu-round check to generate the fix:
https://github.com/elmarco/clang-tools-extra
Signed-off-by: Marc-André Lureau <[email protected]>
Signed-off-by: Samuel Thibault <[email protected]>
|
e88718fc0b0399147327adfb369793407482a895
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/e88718fc0b0399147327adfb369793407482a895
|
2017-07-15 14:28:25+02:00
|
s390x/gdb: add gs registers
Let's provide the guarded storage registers via gdb server.
Signed-off-by: Christian Borntraeger <[email protected]>
|
86158a2a2b81f075c84d0b95c6d72b98dbf1dc61
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/86158a2a2b81f075c84d0b95c6d72b98dbf1dc61
|
2017-07-14 12:29:49+02:00
|
slirp: Handle error returns from slirp_send() in sosendoob()
The code in sosendoob() assumes that slirp_send() always
succeeds, but it might return an OS error code (for instance
if the other end has disconnected). Catch these and return
the caller either -1 on error or the number of urgent bytes
actually written. (None of the callers check this return
value currently, though.)
Signed-off-by: Peter Maydell <[email protected]>
Reviewed-by: Dr. David Alan Gilbert <[email protected]>
Signed-off-by: Samuel Thibault <[email protected]>
|
0b466065eba289c437e3edc2e97144fc5cd6a889
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/0b466065eba289c437e3edc2e97144fc5cd6a889
|
2017-07-15 14:28:25+02:00
|
block: expose crypto option names / defs to other drivers
The block/crypto.c defines a set of QemuOpts that provide
parameters for encryption. This will also be needed by
the qcow/qcow2 integration, so expose the relevant pieces
in a new block/crypto.h header. Some helper methods taking
QemuOpts are changed to take QDict to simplify usage in
other places.
Reviewed-by: Max Reitz <[email protected]>
Reviewed-by: Eric Blake <[email protected]>
Reviewed-by: Alberto Garcia <[email protected]>
Signed-off-by: Daniel P. Berrange <[email protected]>
Message-id: [email protected]
Signed-off-by: Max Reitz <[email protected]>
|
306a06e5f766acaf26b71397a5692c65b65a61c7
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/306a06e5f766acaf26b71397a5692c65b65a61c7
|
2017-07-11 17:44:55+02:00
|
s390x/kvm: enable guarded storage
Introduce guarded storage support for KVM guests on s390.
We need to enable the capability, extend machine check validity,
sigp store-additional-status-at-address, and migration.
The feature is fenced for older machine type versions.
Signed-off-by: Fan Zhang <[email protected]>
Reviewed-by: Cornelia Huck <[email protected]>
Signed-off-by: Christian Borntraeger <[email protected]>
|
62deb62d999cf9e2be61272c6b720104f764bd6a
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/62deb62d999cf9e2be61272c6b720104f764bd6a
|
2017-07-14 12:29:49+02:00
|
vl: fix breakage of -tb-size
Commit e7b161d573 ("vl: add tcg_enabled() for tcg related code") adds
a check to exit the program when !tcg_enabled() while parsing the -tb-size
flag.
It turns out that when the -tb-size flag is evaluated, tcg_enabled() can
only return 0, since it is set (or not) much later by configure_accelerator().
Fix it by unconditionally exiting if the flag is passed to a QEMU binary
built with !CONFIG_TCG.
Signed-off-by: Emilio G. Cota <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
|
f940488feaca394ccc68e0595b4c3a9017f16e45
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/f940488feaca394ccc68e0595b4c3a9017f16e45
|
2017-07-14 12:04:42+02:00
|
stream: Switch stream_run() to byte-based
We are gradually converting to byte-based interfaces, as they are
easier to reason about than sector-based. Change the internal
loop iteration of streaming to track by bytes instead of sectors
(although we are still guaranteed that we iterate by steps that
are sector-aligned).
Signed-off-by: Eric Blake <[email protected]>
Reviewed-by: John Snow <[email protected]>
Reviewed-by: Jeff Cody <[email protected]>
Reviewed-by: Kevin Wolf <[email protected]>
Signed-off-by: Kevin Wolf <[email protected]>
|
d535435f4a3968a897803d38bf1642f3b644979a
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/d535435f4a3968a897803d38bf1642f3b644979a
|
2017-07-10 13:18:06+02:00
|
hw/arm/exynos: Declare local variables in some order
Bring some more readability by declaring local function variables: first
initialized ones and then the rest (with reversed-christmas-tree order).
Signed-off-by: Krzysztof Kozlowski <[email protected]>
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
Signed-off-by: Peter Maydell <[email protected]>
|
310150c000800dc47d7b5db0e02b2e517d13886e
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/310150c000800dc47d7b5db0e02b2e517d13886e
|
2017-06-13 14:56:57+01:00
|
pseries: Reset CPU compatibility mode
Currently, the CPU compatibility mode is set when the cpu is initialized,
then again when the guest negotiates features. This means if a guest
negotiates a compatibility mode, then reboots, that compatibility mode
will be retained across the reset.
Usually that will get overridden when features are negotiated on the next
boot, but it's still not really correct. This patch moves the initial set
up of the compatibility mode from cpu init to reset time. The mode *is*
retained if the reboot was caused by the feature negotiation (it might
be important in that case, though it's unlikely).
Signed-off-by: David Gibson <[email protected]>
Reviewed-by: Alexey Kardashevskiy <[email protected]>
Reviewed-by: Michael Roth <[email protected]>
Tested-by: Andrea Bolognani <[email protected]>
|
66d5c492dd3a92fbb6f01f3957fbe3fe5a18613e
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/66d5c492dd3a92fbb6f01f3957fbe3fe5a18613e
|
2017-06-30 14:03:31+10:00
|
spapr: Clean up RTAS set-indicator
In theory the RTAS set-indicator call can be used for a number of
"indicators" defined by PAPR. In practice the only ones we're ever likely
to implement are those used for Dynamic Reconfiguration (i.e. hotplug).
Because of this, the current implementation determines the associated DRC
object, before dispatching based on the type of indicator.
However, this means we also need a check that we're dealing with a DR
related indicator at all, which duplicates some of the logic from the
switch further down.
Even though it means a bit of code duplication, things work out cleaner if
we delegate the DRC lookup to the individual indicator type functions -
and it also allows some further cleanups.
While we're there, remove references to "sensor", a copy/paste artefact
from the related, but distinct "get-sensor" call.
Signed-off-by: David Gibson <[email protected]>
Reviewed-by: Michael Roth <[email protected]>
Acked-by: Michael Roth <[email protected]>
|
7b7258f810d2bd40e2fb99c469c5db318d6c3d92
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/7b7258f810d2bd40e2fb99c469c5db318d6c3d92
|
2017-06-08 14:38:26+10:00
|
char: cast ARRAY_SIZE() as signed to silent warning on empty array
chardev/char.c: In function 'chardev_name_foreach':
chardev/char.c:546:19: error: comparison of unsigned expression < 0 is always false [-Werror=type-limits]
for (i = 0; i < ARRAY_SIZE(chardev_alias_table); i++) {
^
Signed-off-by: Philippe Mathieu-Daudé <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Marc-André Lureau <[email protected]>
|
c7e47c63e0362ffded57db38684b88c270cff65f
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/c7e47c63e0362ffded57db38684b88c270cff65f
|
2017-06-02 11:33:35+04:00
|
blockjob: remove unnecessary check
!job is always checked prior to the call, drop it from here.
Reviewed-by: Stefan Hajnoczi <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Reviewed-by: Jeff Cody <[email protected]>
Message-id: [email protected]
Signed-off-by: Jeff Cody <[email protected]>
|
6573d9c63885aaf533366ab5c68318d1cf1a0fcc
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/6573d9c63885aaf533366ab5c68318d1cf1a0fcc
|
2017-05-24 16:38:51-04:00
|
iotests: 055: Don't attach the target image already for drive-backup
Double attach is not a valid usage of the target image, drive-backup
will open the blockdev itself so skip the add_drive call in this case.
Signed-off-by: Fam Zheng <[email protected]>
Reviewed-by: Max Reitz <[email protected]>
Signed-off-by: Kevin Wolf <[email protected]>
|
4797aeabdc61d7bbf9ef0cb9e25fb539912bb7f3
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/4797aeabdc61d7bbf9ef0cb9e25fb539912bb7f3
|
2017-05-11 11:08:40+02:00
|
pc-bios/s390-ccw: Get Block Limits VPD device data
The "Block Limits" Inquiry VPD page is optional for any SCSI device,
but if it's supported it provides a hint of the maximum I/O transfer
length for this particular device. If this page is supported by the
disk, let's issue that Inquiry and use the minimum of it and the
SCSI controller limit. That will cover this scenario:
qemu-system-s390x ...
-device virtio-scsi-ccw,id=scsi0,max_sectors=32768 ...
-drive file=/dev/sda,if=none,id=drive0,format=raw ...
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,
drive=drive0,id=disk0,max_io_size=1048576
controller: 32768 sectors x 512 bytes/sector = 16777216 bytes
disk: 1048576 bytes
Now that we have a limit for a virtio-scsi disk, compare that with the
limit for the virtio-scsi controller when we actually build the I/O.
The minimum of these two limits should be the one we use.
Signed-off-by: Eric Farman <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Cornelia Huck <[email protected]>
|
fe921fc8b7e92020bb140079a9f47f14fb8e9075
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/fe921fc8b7e92020bb140079a9f47f14fb8e9075
|
2017-05-19 12:29:01+02:00
|
tcx: ensure tcx_set_dirty() also invalidates the 24-bit plane and cplane
Signed-off-by: Mark Cave-Ayland <[email protected]>
Reviewed-by: Gerd Hoffmann <[email protected]>
|
4b865c28099ddd365062f46dd1ad83c03b2468eb
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/4b865c28099ddd365062f46dd1ad83c03b2468eb
|
2017-04-21 09:02:04+01:00
|
s390x: initialize flic before I/O subsystems
Let's have a flic before we move on to initialize more specific
subsystems that make use of it.
Signed-off-by: Fei Li <[email protected]>
Reviewed-by: Cornelia Huck <[email protected]>
Signed-off-by: Cornelia Huck <[email protected]>
|
c572d3f313a3580bc2a1ec7c14a25a2ac40c32ca
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/c572d3f313a3580bc2a1ec7c14a25a2ac40c32ca
|
2017-04-21 09:32:09+02:00
|
s390x/pci: make printf always compile in debug output
Wrapped printf calls inside debug macros (DPRINTF) in `if` statement.
This will ensure that printf function will always compile even if debug
output is turned off and, in turn, will prevent bitrot of the format
strings.
Signed-off-by: Danil Antonov <[email protected]>
Message-Id: <CA+KKJYBi31Bs7DtVdzZdwG2t+u5+FGiAhQpd3pqJzUX1O8Cprg@mail.gmail.com>
[CH: remove now misleading comments]
Signed-off-by: Cornelia Huck <[email protected]>
|
229913f0ef3807b5cf4eecd5a0ef8133ff6dbbcb
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/229913f0ef3807b5cf4eecd5a0ef8133ff6dbbcb
|
2017-04-21 09:32:09+02:00
|
vfio: Set MemoryRegionOps:max_access_size and min_access_size
Sets valid.max_access_size and valid.min_access_size to ensure safe
8-byte accesses to vfio. Today, 8-byte accesses are broken into pairs
of 4-byte calls that goes unprotected:
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc0, 0x2020c, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc4, 0xa0000, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
which occasionally leads to:
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc0, 0x2030c, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc0, 0x1000c, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc4, 0xb0000, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc4, 0xa0000, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
causing strange errors in guest OS. With this patch, such accesses
are protected by the same lock guard:
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc0, 0x2000c, 4)
vfio_region_write (0001:03:00.0:region1+0xc4, 0xb0000, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
This happens because the 8-byte write should be broken into 4-byte
writes by memory.c:access_with_adjusted_size() in order to be under
the same lock. Today, it's done in exec.c:address_space_write_continue()
which was able to handle only 4 bytes due to a zero'ed
valid.max_access_size (see exec.c:memory_access_size()).
Signed-off-by: Jose Ricardo Ziviani <[email protected]>
Signed-off-by: Alex Williamson <[email protected]>
|
15126cba8618ac6cf4dde320ff9cd96ad0640d5d
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/15126cba8618ac6cf4dde320ff9cd96ad0640d5d
|
2017-05-03 14:52:34-06:00
|
qemu-io-cmds: Assert that global and nofile commands don't use ct->perms
It would be a bug for a command with the CMD_NOFILE_OK or
CMD_FLAG_GLOBAL flags set to also set the ct->perms field,
because the former says "OK for a file not to be open"
but the latter is a check on a file.
Add an assertion in qemuio_add_command() so we can catch that
sort of buggy command definition immediately rather than it
being a bug that only manifests when a particular set of
command line options is used.
(Coverity gets confused about this (CID 1371723) and reports
that we might dereference a NULL blk pointer in this case,
because it can't tell that that code path never happens with
the cmdinfo_t that we have. This commit won't help unconfuse
it, but it does fix the underlying issue.)
Signed-off-by: Peter Maydell <[email protected]>
Message-id: [email protected]
Signed-off-by: Max Reitz <[email protected]>
|
6aabeb58391a33cda7e2b406adb431a5ef7e8eea
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/6aabeb58391a33cda7e2b406adb431a5ef7e8eea
|
2017-04-03 17:11:40+02:00
|
e500,book3s: mfspr 259: Register mapped/aliased SPRG3 user read
This patch registers mfspr 259 for Book3S and e500 family cores
following this research:
mfspr 259 provides read-only mapped user access to SPRG3(SPR 275) according to:
- PowerISA 2.02, Book III (documents implementation starting with POWER4+ @ p20)
- IBM PowerPC 970MP RISC Microprocessor User's Manual v2.1, page 48
- Amit Singh: "Mac OS X Internals: A Systems Approach" on 970 and 970FX cores:
He demonstrates mfspr 259 reading TLS data from Mac OS X on G5 on page 588
- NXP documents it in the Core Reference Manuals of: e500, e500mc and e5500
- getcpu() of the 32 & 64-bit Book3S Linux vDSOs use it to read the core number
mfspr 259 does not appear to be implemented in these cores according to:
- 74xx series: MPC7410/MPC7400 and MPC7450 RISC Microprocessor Reference Manuals
- 4xx series: PPC440 Processor User's Manual, Revision 1.09 by AMCC
- 750 series: IBM PowerPC 750CL RISC Microprocessor User's Manual
- e200 series: e200z4 Power Architectureâ Core Reference Manual
Implementation: gen_spr_usprg3() is called from init_proc_book3s_common()
(covers the 970 and POWER cores) and init_proc_e500() (covers the e500 family)
to register spr_read_ureg() in the same way which it already provides
the mapped SPR access for SPR_USPRG4-7 in gen_spr_usprgh() for cores
which have the same read-only mapped SPRG register access for SPRG4-7.
Verified using Linux by pinning a thread to a core and checking sched_getcpu()
using qemu-system-ppc64 -M pseries -cpu POWER8 using MTTCG on a x86_64 host.
Signed-off-by: Bernhard Kaindl <[email protected]>
Reviewed-by: Stefan Resch <[email protected]>
Signed-off-by: David Gibson <[email protected]>
|
b1c897d58729bd5cb390afa4e311dc42b38baf77
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/b1c897d58729bd5cb390afa4e311dc42b38baf77
|
2017-04-26 12:41:56+10:00
|
fix :cirrus_vga fix OOB read case qemu Segmentation fault
check the validity of parameters in cirrus_bitblt_rop_fwd_transp_xxx
and cirrus_bitblt_rop_fwd_xxx to avoid the OOB read which causes qemu Segmentation fault.
After the fix, we will touch the assert in
cirrus_invalidate_region:
assert(off_cur_end >= off_cur);
Signed-off-by: fangying <[email protected]>
Signed-off-by: hangaohuai <[email protected]>
Message-id: [email protected]
Signed-off-by: Gerd Hoffmann <[email protected]>
|
215902d7b6fb50c6fc216fc74f770858278ed904
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/215902d7b6fb50c6fc216fc74f770858278ed904
|
2017-03-16 08:58:15+01:00
|
bsd-user: align use of mmap_lock to that of linux-user
The introduction of stricter mmap_lock checking in translate-all broke
the BSD user build. The working mmap_lock functions were hidden behind
CONFIG_USE_NPTL which is never defined. This patch brings them inline
with linux-user.
Despite the disapearence of the comment "We aren't threadsafe to start
with..." this doesn't make bsd-user so. It will still need the rest of
the fixes that have been done in linux-user ported over.
Signed-off-by: Alex Bennée <[email protected]>
Reviewed-by: Paolo Bonzini <[email protected]>
|
95992b674c43339d0b313dd79fa8cc45ba22eab8
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/95992b674c43339d0b313dd79fa8cc45ba22eab8
|
2017-03-28 10:50:40+01:00
|
ohci: relax link check
The strict td link limit added by commit "95ed569 usb: ohci: limit the
number of link eds" causes problems with macos guests. Lets raise the
limit.
Reported-by: Programmingkid <[email protected]>
Reported-by: Howard Spoelstra <[email protected]>
Signed-off-by: Gerd Hoffmann <[email protected]>
Reviewed-by: BALATON Zoltan <[email protected]>
Reviewed-by: John Arbuckle <[email protected]>
Message-id: [email protected]
|
ab6b1105a2259c7072905887f71caa850ce63190
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/ab6b1105a2259c7072905887f71caa850ce63190
|
2017-03-09 09:46:13+01:00
|
keyval: Restrict key components to valid QAPI names
Until now, key components are separated by '.'. This leaves little
room for evolving the syntax, and is incompatible with the __RFQDN_
prefix convention for downstream extensions.
Since key components will be commonly used as QAPI member names by the
QObject input visitor, we can just as well borrow the QAPI naming
rules here: letters, digits, hyphen and period starting with a letter,
with an optional __RFQDN_ prefix for downstream extensions.
Signed-off-by: Markus Armbruster <[email protected]>
Reviewed-by: Kevin Wolf <[email protected]>
Message-Id: <[email protected]>
|
f740048323398ebde9575a5730bf6d9f2a237f08
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/f740048323398ebde9575a5730bf6d9f2a237f08
|
2017-03-07 16:07:47+01:00
|
target/ppc: Correct SDR1 masking
SDR_64_HTABORG, which indicates the bits of the SDR1 register to use for
the base of a 64-bit machine's hashed page table (HPT) isn't correct. It
includes the top 46 bits of the register, but in fact the top 4 bits must
be zero (according to the ISA v2.07). No actual implementation has
supported close to 2^60 bytes of physical address space, so it's kind of
irrelevant, but we might as well correct this.
In addition, although we checked for bad size values in SDR1, we never
reported an error if entirely invalid bits were set there. Add this check
to ppc_store_sdr1().
Reported-by: Suraj Jitindar Singh <[email protected]>
Signed-off-by: David Gibson <[email protected]>
|
e78308fd3959c2694c8c366efdccacdd11997ac8
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/e78308fd3959c2694c8c366efdccacdd11997ac8
|
2017-03-01 11:23:39+11:00
|
sd: sdhci: Remove block count enable check in single block transfers
In SDHCI protocol, the 'Block count enable' bit of the Transfer
Mode register is relevant only in multi block transfers. We need
not check it in single block transfers.
Signed-off-by: Prasad J Pandit <[email protected]>
Message-id: [email protected]
Reviewed-by: Alistair Francis <[email protected]>
Signed-off-by: Peter Maydell <[email protected]>
|
241999bf4c0dd75d300ceee46f7ad28b3a39fe97
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/241999bf4c0dd75d300ceee46f7ad28b3a39fe97
|
2017-02-28 12:08:15+00:00
|
niagara: check if a serial port is available
Reported-by: Markus Armbruster <[email protected]>
Reviewed-by: Markus Armbruster <[email protected]>
Signed-off-by: Artyom Tarasenko <[email protected]>
|
a5a08302d44a8b1a8c5819b1411002f85bb5f847
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/a5a08302d44a8b1a8c5819b1411002f85bb5f847
|
2017-02-26 22:46:08+01:00
|
block/rbd: parse all options via bdrv_parse_filename
Get rid of qemu_rbd_parsename in favor of bdrv_parse_filename.
This simplifies a lot of the parsing as well, as we can treat everything
a bit simpler since nonexistent options are simply NULL pointers instead
of empty strings.
An important item to note:
Ceph has many extra option values that can be specified as key/value
pairs. This was handled previously in the driver by extracting the
values that the QEMU driver cared about, and then blindly passing all
extra options to rbd after splitting them into key/value pairs, and
cleaning up any special character escaping.
The practice is continued in this patch; there is an option
"keyvalue-pairs" that is populated with all the key/value pairs that the
QEMU driver does not care about. These key/value pairs will override
any settings in the 'conf' configuration file, just as they did before.
Reviewed-by: Eric Blake <[email protected]>
Signed-off-by: Jeff Cody <[email protected]>
|
c7cacb3e7a2e9fdf929c993b98268e4179147cbb
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/c7cacb3e7a2e9fdf929c993b98268e4179147cbb
|
2017-02-28 11:32:31-05:00
|
cpu-exec: remove unnecessary check of cpu->exit_request
The cpu->exit_request check in cpu_loop_exec_tb is unnecessary,
because cpu->tcg_exit_req is always set after cpu->exit_request.
So let the TB exit and we will pick up the exit request later
in cpu_handle_interrupt.
Signed-off-by: Paolo Bonzini <[email protected]>
|
55ac0a9bf4e1b1adfc7d73586a7aa085f58c9851
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/55ac0a9bf4e1b1adfc7d73586a7aa085f58c9851
|
2017-02-24 15:51:19+01:00
|
vfio: introduce vfio_get_vaddr()
A cleanup for vfio_iommu_map_notify(). Now we will fetch vaddr even if
the operation is unmap, but it won't hurt much.
One thing to mention is that we need the RCU read lock to protect the
whole translation and map/unmap procedure.
Acked-by: Alex Williamson <[email protected]>
Reviewed-by: David Gibson <[email protected]>
Signed-off-by: Peter Xu <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
|
4a4b88fbe1a95e80a2e29830e69e1deded407fc1
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/4a4b88fbe1a95e80a2e29830e69e1deded407fc1
|
2017-02-17 21:52:31+02:00
|
util/cutils: Clean up control flow around qemu_strtol() a bit
Reorder check_strtox_error() to make it obvious that we always store
through a non-null @endptr.
Transform
if (some error) {
error case ...
err = value for error case;
} else {
normal case ...
err = value for normal case;
}
return err;
to
if (some error) {
error case ...
return value for error case;
}
normal case ...
return value for normal case;
Signed-off-by: Markus Armbruster <[email protected]>
Reviewed-by: Eric Blake <[email protected]>
Message-Id: <[email protected]>
|
4baef2679e029c76707be1e2ed54bf3dd21693fe
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/4baef2679e029c76707be1e2ed54bf3dd21693fe
|
2017-02-23 20:35:35+01:00
|
net: Mark 'vlan' parameter as deprecated
The 'vlan' parameter is a continuous source of confusion for the users,
many people mix it up with the more common term VLAN (the link layer
packet encapsulation), and even if they realize that the QEMU 'vlan' is
rather some kind of network hub emulation, there is still a high risk
that they configure their QEMU networking in a wrong way with this
parameter (e.g. by hooking NICs together, so they get a 'loopback'
between one and the other NIC).
Thus at one point in time, we should finally get rid of the 'vlan'
feature in QEMU. Let's do a first step in this direction by declaring
the 'vlan' parameter as deprecated and informing the users to use the
'netdev' parameter instead.
Signed-off-by: Thomas Huth <[email protected]>
Signed-off-by: Jason Wang <[email protected]>
|
a2dbe1356faff3cb613ae83b77c484a203be5f15
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/a2dbe1356faff3cb613ae83b77c484a203be5f15
|
2017-02-15 11:18:57+08:00
|
aspeed/smc: handle dummies only in fast read mode
HW works fine in normal read mode with dummy bytes being set. So let's
check this case to not transfer bytes.
Signed-off-by: Cédric Le Goater <[email protected]>
Message-id: [email protected]
Signed-off-by: Peter Maydell <[email protected]>
|
1a6d4fc27d75839b6a0325ef258560fded6ec7d9
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/1a6d4fc27d75839b6a0325ef258560fded6ec7d9
|
2017-02-10 17:40:29+00:00
|
qemu-char: socket backend: disconnect on write error
Socket backend read handler should normally perform a disconnect, however
the read handler may not get a chance to run if the frontend is not ready
(qemu_chr_be_can_write() == 0).
This means that in virtio-serial frontend case if
- the host has disconnected (giving EPIPE on socket write)
- and the guest has disconnected (-> frontend not ready -> backend
will not read)
- and there is still data (frontend->backend) to flush (has to be a really
tricky timing but nevertheless, we have observed the case in production)
This results in virtio-serial trying to flush this data continiously forming
a busy loop.
Solution: react on write error in the socket write handler.
errno is not reliable after qio_channel_writev_full(), so we may not get
the exact EPIPE, so disconnect on any error but QIO_CHANNEL_ERR_BLOCK which
io_channel_send_full() converts to errno EAGAIN.
We must not disconnect right away though, there still may be data to read
(see 4bf1cb0).
Signed-off-by: Anton Nefedov <[email protected]>
Signed-off-by: Denis V. Lunev <[email protected]>
CC: Paolo Bonzini <[email protected]>
CC: Daniel P. Berrange <[email protected]>
CC: Marc-André Lureau <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
|
b0a335e351103bf92f3f9d0bd5759311be8156ac
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/b0a335e351103bf92f3f9d0bd5759311be8156ac
|
2017-02-16 14:06:55+01:00
|
sd: sdhci: check data length during dma_memory_read
While doing multi block SDMA transfer in routine
'sdhci_sdma_transfer_multi_blocks', the 's->fifo_buffer' starting
index 'begin' and data length 's->data_count' could end up to be same.
This could lead to an OOB access issue. Correct transfer data length
to avoid it.
Cc: [email protected]
Reported-by: Jiang Xin <[email protected]>
Signed-off-by: Prasad J Pandit <[email protected]>
Reviewed-by: Peter Maydell <[email protected]>
Message-id: [email protected]
Signed-off-by: Peter Maydell <[email protected]>
|
42922105beb14c2fc58185ea022b9f72fb5465e9
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/42922105beb14c2fc58185ea022b9f72fb5465e9
|
2017-02-07 18:29:59+00:00
|
gdbstub.c: fix GDB connection segfault caused by empty machines
This patch is to fix the segmentation fault caused by attaching
GDB to a QEMU instance initialized with "-M none" option.
The bug can be reproduced by
> ./qemu-system-x86_64 -M none -nographic -S -s
and attach a GDB to it by
> gdb -ex 'target remote :1234
The segmentation fault was originally caused by trying to read
the information about CPU when communicating with GDB. However,
it's impossible for any control flow to exist on an empty machine,
nor can CPU's be hot plugged to an empty machine later by QOM
commands. So I think simply disabling GDB connections on empty
machines makes sense.
Signed-off-by: Ziyue Yang <[email protected]>
Reviewed-by: Thomas Huth <[email protected]>
Signed-off-by: Michael Tokarev <[email protected]>
|
508b4ecc3935f0cffb6f8e302fb84941dae940c9
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/508b4ecc3935f0cffb6f8e302fb84941dae940c9
|
2017-01-24 23:26:53+03:00
|
arm: virt: Fix segmentation fault when specifying an unsupported CPU
Using -cpu cortex-a9 (or any other unsupported CPU) with the virt
board will cause QEMU to segmentation fault. This bug was introduced
in commit 9ac4ef77, which incorrectly added a NULL terminator when
converting the VirtBoardInfo array into a simple array of strings
defining the valid CPUs. The cpuname_valid() loop already has
a termination condition based on ARRAY_SIZE, so the NULL is
spurious and causes the strcmp() to segfault if we reach it.
Delete the NULL.
Signed-off-by: Shannon Zhao <[email protected]>
Message-id: [email protected]
[PMM: expanded commit message]
Reviewed-by: Peter Maydell <[email protected]>
Signed-off-by: Peter Maydell <[email protected]>
|
abf3a4e5eeab9b1d4dea4149a9e77d970fe83fc5
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/abf3a4e5eeab9b1d4dea4149a9e77d970fe83fc5
|
2017-01-20 11:15:08+00:00
|
xen-platform: add missing disk unplug option
The Xen HVM unplug protocol [1] specifies a mechanism to allow guests to
request unplug of 'aux' disks (which is stated to mean all IDE disks,
except the primary master). This patch adds support for that unplug request.
NOTE: The semantics of what happens if unplug of all disks and 'aux' disks
is simultaneously requests is not clear. The patch makes that
assumption that an 'all' request overrides an 'aux' request.
[1] http://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=docs/misc/hvm-emulated-unplug.markdown
Signed-off-by: Paul Durrant <[email protected]>
Reviewed-by: Stefano Stabellini <[email protected]>
----
Cc: Stefano Stabellini <[email protected]>
Cc: Anthony Perard <[email protected]>
Cc: Paolo Bonzini <[email protected]>
Cc: Richard Henderson <[email protected]>
Cc: Eduardo Habkost <[email protected]>
Cc: "Michael S. Tsirkin" <[email protected]>
Cc: John Snow <[email protected]>
|
ae4d2eb273b167dad748ea4249720319240b1ac2
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/ae4d2eb273b167dad748ea4249720319240b1ac2
|
2017-01-27 15:23:29-08:00
|
ui/vnc: Fix problem with sending too many bytes as server name
If the buffer is not big enough, snprintf() does not return the number
of bytes that have been written to the buffer, but the number of bytes
that would be needed for writing the whole string. By using this value
for the following vnc_write() calls, we send some junk at the end of
the name in case the qemu_name is longer than 1017 bytes, which could
confuse the VNC clients. Fix this by adding an additional size check
here.
Buglink: https://bugs.launchpad.net/qemu/+bug/1637447
Signed-off-by: Thomas Huth <[email protected]>
Reviewed-by: Eric Blake <[email protected]>
Message-id: [email protected]
Signed-off-by: Gerd Hoffmann <[email protected]>
|
97efe4f961dcf5a0126baa75e8a6bff66d33186f
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/97efe4f961dcf5a0126baa75e8a6bff66d33186f
|
2017-01-10 08:14:20+01:00
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.