Convert the TCG ARM target to using an (index,value) list for migrating
coprocessors. The primary benefit of the (index,value) list is for
passing state between KVM and QEMU, but it works for TCG-to-TCG
migration as well and is a useful self-contained first step.
Signed-off-by: Peter Maydell
Paolo Bonzini pbonz...@redhat.com suggested the following test case:
1. Launch a guest and wait at the GRUB boot menu:
qemu-system-x86_64 -enable-kvm -m 1024 \
-drive if=none,cache=none,file=test.img,id=foo,werror=stop,rerror=stop
-device virtio-blk-pci,drive=foo,id=virtio0,addr=4
2.
On 3 June 2013 15:23, Richard Henderson r...@twiddle.net wrote:
On 06/02/2013 10:15 AM, Peter Maydell wrote:
So for a new architecture how do we determine whether we need
to fiddle with the start address or not? (More specifically,
is aarch64 going to need a linker script or just to go in the
On 06/03/2013 07:57 AM, Peter Maydell wrote:
Well, the output of ld --verbose says:
PROVIDE (__executable_start = SEGMENT_START(text-segment,
0x40)); . = SEGMENT_START(text-segment, 0x40) +
SIZEOF_HEADERS;
and objdump of a random aarch64 binary suggests the
text segment
On 06/01/2013 03:35 PM, Peter Maydell wrote:
Basically, removing the ugly direct syscall access seemed nicer
than trying to fix up and render consistent the broken ifdefs :-)
[RHEL5 has glibc2.5 and provides these functions. RHEL4 did not
but we don't build on RHEL4 anyhow because its glib
On 10 May 2013 16:32, Igor Mitsyanko i.mitsya...@gmail.com wrote:
Fix issues in exynos4210 code which were blocking proper memory
migration.
Thanks, applied to arm-devs.next.
-- PMM
On 30 May 2013 00:15, pe...@chubb.wattle.id.au wrote:
Jean-Christophe wrote:
* Unify function and type naming
* use dynamic cast whenever possible
* simplify Debug printf.
* use new style device intialization.
Signed-off-by: Jean-Christophe DUBOIS j...@tribudubois.net
Reviewed-by: Peter
My patch committed at 87f25c12bfeaaa0c41fb857713bbc7e8a9b757dc
was broken. These patches fix the problem in a better way.
Paolo
Paolo Bonzini (2):
gdbstub: fix for commit 87f25c12bfeaaa0c41fb857713bbc7e8a9b757dc
gdbstub: let the debugger resume from guest panicked state
gdbstub.c | 5
While in general we forbid a continue from the guest panicked
state, it makes sense to have an exception for that when continuing
in the debugger. Perhaps the guest entered that state due to a bug,
for example, and we want to continue no matter what.
Signed-off-by: Paolo Bonzini
This commit used the wrong check to prevent an assertion failure.
After this commit, you need to start a guest in the monitor, you
cannot use anymore the c command in the debugger. This is
undesirable. The commit's aim was to prevent a restart
after a KVM internal error or something like that;
One way to reproduce this is to just use a large (200 MB) completely
random initrd. Note this error seems to happen a long time before even
the kernel starts up, so the actual content of the initrd doesn't
matter.
dd if=/dev/urandom of=/tmp/initrd bs=1M count=200
qemu-system-x86_64 -kernel
On 8 May 2013 09:28, Jean-Christophe DUBOIS j...@tribudubois.net wrote:
--- a/include/hw/arm/imx.h
+++ b/include/hw/arm/imx.h
@@ -23,12 +23,10 @@ typedef enum {
uint32_t imx_clock_frequency(DeviceState *s, IMXClk clock);
-void imx_timerp_create(const hwaddr addr,
-
On 8 May 2013 09:28, Jean-Christophe DUBOIS j...@tribudubois.net wrote:
+/*
+ *if we unset the master mode then it ends the ongoing
+ * transfer if any
+ */
nit: missing space between '*' and if'.
thanks
-- PMM
OK I see what's happening. Because I forgot about the -m option, qemu
allocates 128 MB of RAM. It's obviously wrapping around in memory and
overwriting all the low memory.
If you add (eg) -m 1024 it works.
--
You received this bug notification because you are a member of qemu-
devel-ml, which
On 06/02/2013 10:10 AM, Peter Maydell wrote:
+tde-d_ino = tswapal(ino);
+tde-d_off = tswapal(off);
+tde-d_reclen = tswap16(treclen);
+memmove(tde-d_name, de-d_name, namelen + 1);
Wouldn't it be better to do the
On 8 May 2013 09:28, Jean-Christophe DUBOIS j...@tribudubois.net wrote:
For now we support:
* timers (GPT and EPIT)
* serial ports
* ethernet (through the newly added FEC emulator)
* I2C (through the newly added I2C emulator)
+/* add I2C 0 */
+i2c_dev =
The sysfw code to choose between ROM and flash BIOS was a bad idea,
because it triggered different behavior between TCG and KVM. We
deleted the behavior in 1.5, but we left the code around because
it was close to the release. Now it's time to delete it.
Paolo Bonzini (3):
remove read-only
The variable is not written anymore.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/block/pc_sysfw.c | 26 +-
1 file changed, 1 insertion(+), 25 deletions(-)
diff --git a/hw/block/pc_sysfw.c b/hw/block/pc_sysfw.c
index 412d1b0..c6d4be4 100644
---
With the new semantics of pc_sysfw (no -pflash implies old-style ROM setup,
-pflash implies new-style ROM setup), there is no need anymore for a compat
property. Old machines simply will never use -pflash, and thus will always
use old-style setup.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
Move the code to hw/i386, the sole remaining property is available
as !pci_enabled.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
default-configs/i386-softmmu.mak | 1 -
default-configs/x86_64-softmmu.mak | 1 -
hw/block/Makefile.objs | 1 -
hw/i386/Makefile.objs
On 8 May 2013 09:28, Jean-Christophe DUBOIS j...@tribudubois.net wrote:
This is using a ds1338 RTC chip on the i2c bus. This RTC
chip is not present on the real board.
Ideally this should work by the test driver passing
a -device ds1338,something,something argument to
instantiate the RTC and
Coverity complains about two overruns in process_tx_desc(). The
complaints are false positives, but we might as well eliminate
them. The problem is that hdr is defined as an unsigned int,
but then used to offset an array of size 65536, and another of
size 256 bytes. hdr will actually never be
On 12 May 2013 14:14, Peter Maydell peter.mayd...@linaro.org wrote:
On 12 May 2013 13:55, Jean-Christophe DUBOIS j...@tribudubois.net wrote:
In your opinion, is this patch set good enough in its actual state for
inclusion?
Are you expecting anything else from me (beside maybe adding more i.MX
On Mon, 3 Jun 2013 17:06:53 +0200
Paolo Bonzini pbonz...@redhat.com wrote:
My patch committed at 87f25c12bfeaaa0c41fb857713bbc7e8a9b757dc
was broken. These patches fix the problem in a better way.
Looks good to me:
Reviewed-by: Luiz Capitulino lcapitul...@redhat.com
Il 03/06/2013 16:58, Stefan Hajnoczi ha scritto:
Paolo Bonzini pbonz...@redhat.com suggested the following test case:
1. Launch a guest and wait at the GRUB boot menu:
qemu-system-x86_64 -enable-kvm -m 1024 \
-drive if=none,cache=none,file=test.img,id=foo,werror=stop,rerror=stop
** Summary changed:
- large -initrd crashes qemu
+ large -initrd can wrap around in memory causing memory corruption
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1186984
Title:
large -initrd can
On 3 June 2013 16:15, Richard Henderson r...@twiddle.net wrote:
On 06/02/2013 10:10 AM, Peter Maydell wrote:
+tde-d_ino = tswapal(ino);
+tde-d_off = tswapal(off);
+tde-d_reclen = tswap16(treclen);
+
Applied. Thanks.
Regards,
Anthony Liguori
Applied. Thanks.
Regards,
Anthony Liguori
Fix parsing of NBD URIs with IPv6 addresses, broken by v1.4.0-736-gf17c90b
and fix parsing of NBD filenames with hostnames starting with a digit (fixed
by the same commit, but only for NBD URIs):
https://lists.gnu.org/archive/html/qemu-devel/2013-05/msg04719.html
Ján Tomko (2):
qemu-socket:
According to RFC 1123 [1], hostnames can start with a digit too.
[1] http://tools.ietf.org/html/rfc1123#page-13
Signed-off-by: Ján Tomko jto...@redhat.com
---
util/qemu-sockets.c | 13 -
1 file changed, 4 insertions(+), 9 deletions(-)
diff --git a/util/qemu-sockets.c
Otherwise they would get passed to getaddrinfo and fail with:
address resolution failed for [::1]:1234: Name or service not known
(Broken by commit v1.4.0-736-gf17c90b)
Signed-off-by: Ján Tomko jto...@redhat.com
---
block/nbd.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
On 06/03/2013 08:45 AM, Peter Maydell wrote:
+/* The target_dirent type is in what was formerly a
padding
+ * byte at the end of the structure:
+ */
+*(((char *)tde) + treclen - 1) = type;
Maybe easier
On 06/03/2013 04:21 AM, Jani Kokkonen wrote:
@ merge the tlb index into the env+tlb_offset
add x1, x1, x0, lsl #3
For the record, oops. 3 should be CPU_TLB_ENTRY_BITS.
r~
spotted by Coverity,
x86_reg_info_32[] is CPU_NB_REGS32 elements long, so accessing
x86_reg_info_32[CPU_NB_REGS32] will be one element off array.
Signed-off-by: Igor Mammedov imamm...@redhat.com
---
target-i386/cpu.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
This seems to be a bug when building against gtk3.
When building against gtk 3.8.2:
- monitor text gets hidden behind menu bar
- a bar appears on the bottom, growing as the window is resized. When the
contents overflows (a scrollbar appears), this bar is gone.
Building against gtk 2.24.18 / vte
Hello,
I plan to write a PF driver for an SR-IOV card and make the VFs work with QEMU's
VFIO passthrough so I am asking the following design question before trying to
write and push code.
After SR-IOV being enabled on this hardware only one VF function can be active
at a given time.
The PF
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
The LQSPI mode is supposed to work via the automatic CS mode feature
rather than manipulate CS lines itself. Now that auto CS is implemented
remove LQSPIs CS mode override logic. There is still a need to
manipulate the U_PAGE bit in LQSPI
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
The CTRL register was RAZ/WI on some of the RW bits. Even though the
function behind these bits is invalid in QEMU, they should still be
guest accessible. Fix.
Signed-off-by: Peter Crosthwaite peter.crosthwa...@xilinx.com
Reviewed-by: Peter
Applied. Thanks.
Regards,
Anthony Liguori
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
Do 16 words per fifo flush. Increases performance and decreases
debug verbosity. This data depth has no real hardware analogue,
so just go with something that has reasonable performance.
Signed-off-by: Peter Crosthwaite
On 3 June 2013 16:58, Richard Henderson r...@twiddle.net wrote:
On 06/03/2013 08:45 AM, Peter Maydell wrote:
Dunno. It's not actually a char array, so I kind of prefer
to use plain pointer arithmetic for this kind of thing.
Then drop the unnecessary parenthesis
*((char *)tde + trelen - 1)
From: Jean-Christophe DUBOIS j...@tribudubois.net
* Unify function and type naming
* use dynamic cast whenever possible
* simplify Debug printf.
* use new style device intialization.
Signed-off-by: Jean-Christophe DUBOIS j...@tribudubois.net
Reviewed-by: Peter Chubb peter.ch...@nicta.com.au
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
This is worth keeping track of when debugging the device model.
Signed-off-by: Peter Crosthwaite peter.crosthwa...@xilinx.com
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
Reviewed-by: Edgar E. Iglesias edgar.igles...@gmail.com
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
Invalidate the LQSPI cached page when transitioning into LQSPI mode.
Otherwise there is a possibility that the controller will return stale
data to the guest when transitioning back to LQ_MODE after a page
program.
Signed-off-by: Peter
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
The debug printfs on every SPI operation is extremely verbose. Add
a second level of debug for this.
Signed-off-by: Peter Crosthwaite peter.crosthwa...@xilinx.com
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
Reviewed-by: Edgar E.
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
The LQSPI bus attachment supports byte/halfword and misaligned
accesses. Fixed. Refactored the LQSPI cache to be byte-wise
instead of word wise accordingly.
Signed-off-by: Peter Crosthwaite peter.crosthwa...@xilinx.com
Reviewed-by: Peter
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
The end of transfer check was occurring and potentially returning before
the interrupt flag was checked. This means the interrupt will be missed
if it occurs on the last packet. Fix by checking for the interrupt
before checking for the end of
Anthony,
please pull the following changes since commit
6a4e17711442849bf2cc731ccddef5a2a2d92d29:
From: Igor Mitsyanko i.mitsya...@samsung.com
Even if we do not register newly created RAM MemoryRegion for migration with
vmstate_register_ram_global() function, ram_save_setup() still saves this region
to snapshot file with empty idstr==. Consequently this results in error during
VM loading in
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
The data_count variable was being reset on every transfer, including
DMA transfer resumptions. This is incorrect, it should only be set
on a new command.
Manifests as a bug when using ADMA and there is a timer delay between
ADMA frames where
On 05/30/2013 06:34 AM, Stefan Hajnoczi wrote:
@drive-backup
Start a point-in-time copy of a block device to a new destination. The
status of ongoing drive-backup operations can be checked with
query-block-jobs where the BlockJobInfo.type field has the value 'backup'.
The operation can be
** Changed in: qemu
Status: New = Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1186935
Title:
[1.5] QEMU monitor gets overlapped by GTK menu bar
Status in QEMU:
Confirmed
Bug
On 05/30/2013 06:34 AM, Stefan Hajnoczi wrote:
It is not necessary to check that we can find a protocol block driver
since we create or open the image file. This produces the error that we
need anyway.
Besides, the QERR_INVALID_BLOCK_FORMAT is inappropriate since the
protocol is incorrect
On 05/30/2013 06:34 AM, Stefan Hajnoczi wrote:
Use bdrv_getlength() for its byte units and error return instead of
bdrv_get_geometry().
Reported-by: Kevin Wolf kw...@redhat.com
Signed-off-by: Stefan Hajnoczi stefa...@redhat.com
---
blockdev.c | 10 +++---
1 file changed, 7
I'm facing two problems lately wrt QMP patch review: increasingly
lack of bandwidth and lack of background in so many different areas
that are getting new QMP commands almost every week.
In order to help me mitigate this problem, I'm adding Eric and Markus
(besides me) as maintainers of the
Hi,
This is an small update on QMP/HMP/QAPI mainternership. Please, check
individual patches for details.
Luiz Capitulino (2):
MAINTAINERS: new maintainers for qapi-schema.json
MAINTAINERS: split Monitor (QMP/HMP) entry
MAINTAINERS | 24 ++--
1 file changed, 22
Michael Roth mdr...@linux.vnet.ibm.com writes:
When CHR_EVENT_OPEN was initially added, it was CHR_EVENT_RESET,
and it was issued as a bottom-half:
86e94dea5b740dad65446c857f6959eae43e0ba6
Which we basically used to print out a greeting/prompt for the
monitor.
AFAICT the only reason this
On 20 May 2013 16:16, Peter Maydell peter.mayd...@linaro.org wrote:
These patches clean up configure's handling of the list of known
targets. Firstly we autogenerate the default list based on the
set of default-config files; this reduces by 1 the number of
places that need editing when a new
gtk 3.8.2
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1186935
Title:
[1.5] QEMU monitor gets overlapped by GTK menu bar
Status in QEMU:
New
Bug description:
The QEMU minitor gets partially
This entry doesn't reflect reality for a few years now. This commit
splits it into Human Monitor (HMP), QAPI and QMP. Markus is dropped
as a maintainer.
This is what we have been for the last few years. Also, it's going
to help me to offload some of this work to someone else in the near
future.
On 05/30/2013 06:34 AM, Stefan Hajnoczi wrote:
This patch adds a transactional version of the drive-backup QMP command.
It allows atomic snapshots of multiple drives along with automatic
cleanup if there is a failure to start one of the backup jobs.
Note that QMP events are emitted for block
Hi,
With the current git source (f10acc8b38d65a66ffa0588a036489d7fa6a593e),
`qemu-system-x86_64 -enable-kvm` fails to run with the following error:
kvm_set_phys_mem: error unregistering overlapping slot: Invalid argument
After this message, qemu aborts. Reverting the following commit on top
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
The real hardware does not produce interrupts in LQSPI mode. Inhibit
generation of interrupts when the LQ_MODE bit is set.
Signed-off-by: Peter Crosthwaite peter.crosthwa...@xilinx.com
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
On 06/03/2013 11:17 AM, Luiz Capitulino wrote:
This entry doesn't reflect reality for a few years now. This commit
splits it into Human Monitor (HMP), QAPI and QMP. Markus is dropped
as a maintainer.
This is what we have been for the last few years. Also, it's going
to help me to offload
On Mon, Jun 03, 2013 at 12:17:00PM -0500, Anthony Liguori wrote:
Michael Roth mdr...@linux.vnet.ibm.com writes:
When CHR_EVENT_OPEN was initially added, it was CHR_EVENT_RESET,
and it was issued as a bottom-half:
86e94dea5b740dad65446c857f6959eae43e0ba6
Which we basically used to
On 06/03/2013 11:17 AM, Luiz Capitulino wrote:
Hi,
This is an small update on QMP/HMP/QAPI mainternership. Please, check
individual patches for details.
Luiz Capitulino (2):
MAINTAINERS: new maintainers for qapi-schema.json
MAINTAINERS: split Monitor (QMP/HMP) entry
Series:
On Mon, 03 Jun 2013 11:24:58 -0600
Eric Blake ebl...@redhat.com wrote:
On 06/03/2013 11:17 AM, Luiz Capitulino wrote:
This entry doesn't reflect reality for a few years now. This commit
splits it into Human Monitor (HMP), QAPI and QMP. Markus is dropped
as a maintainer.
This is what
Hi; here's the latest arm-devs pullreq. I had a lot of
cc'd mail to wade through putting this together so I wouldn't
be surprised if I missed a patch somewhere; if so please
ping the relevant patch.
Please pull.
thanks
-- PMM
The following changes since commit
On Mon, 03 Jun 2013 11:27:51 -0600
Eric Blake ebl...@redhat.com wrote:
On 06/03/2013 11:17 AM, Luiz Capitulino wrote:
Hi,
This is an small update on QMP/HMP/QAPI mainternership. Please, check
individual patches for details.
Luiz Capitulino (2):
MAINTAINERS: new maintainers for
This should be fixed by Xiao's fix double free the memslot in
kvm_set_phys_mem patch.
On Mon, Jun 3, 2013 at 10:23 AM, Peter Wu lekenst...@gmail.com wrote:
Hi,
With the current git source (f10acc8b38d65a66ffa0588a036489d7fa6a593e),
`qemu-system-x86_64 -enable-kvm` fails to run with the
Pulled. Thanks.
Regards,
Anthony Liguori
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
QSPI has a bigger FIFO than the regular SPI controller. Differentiate
between the two with correct FIFO sizes for each.
This is the first piece of class data for SPIPS, so this patch sees
the creation of the XilinxSPIPSClass definition and
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
You really need this is you want to track a guest banging on LQSPI.
Signed-off-by: Peter Crosthwaite peter.crosthwa...@xilinx.com
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
Reviewed-by: Edgar E. Iglesias edgar.igles...@gmail.com
From: Jean-Christophe DUBOIS j...@tribudubois.net
There is no common code between these 2 timer implementation.
So it is better to split them.
Signed-off-by: Jean-Christophe DUBOIS j...@tribudubois.net
Message-id: 1368990197-19694-1-git-send-email-...@tribudubois.net
Signed-off-by: Peter Maydell
When CHR_EVENT_OPEN was initially added, it was CHR_EVENT_RESET,
and it was issued as a bottom-half:
86e94dea5b740dad65446c857f6959eae43e0ba6
Which we basically used to print out a greeting/prompt for the
monitor.
AFAICT the only reason this was ever done in a BH was because in
some cases we'd
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
This interrupt is not risen after the last block is written to sd. It
is mutually exclusive with the end of transfer conditions. Fix.
Signed-off-by: Peter Crosthwaite peter.crosthwa...@xilinx.com
Reviewed-by: Igor Mitsyanko
From: Igor Mitsyanko i.mitsya...@samsung.com
Exynos SoC was misusing memory_region_init_ram_ptr(): this interface can safely
be used only for memory regions which size is a multiple of target page size.
Change chipid_and_omr memory to an mmio region to fix this.
Signed-off-by: Igor Mitsyanko
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
By default these interrupts are clear on read.
Signed-off-by: Peter Crosthwaite peter.crosthwa...@xilinx.com
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
Reviewed-by: Edgar E. Iglesias edgar.igles...@gmail.com
Message-id:
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
SPI has a mode where it automatically starts based on tx fifo
occupancy. Implemented.
Signed-off-by: Peter Crosthwaite peter.crosthwa...@xilinx.com
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
Reviewed-by: Edgar E. Iglesias
On Mon, 2013-06-03 at 18:33 +0200, Benoît Canet wrote:
Hello,
I plan to write a PF driver for an SR-IOV card and make the VFs work with
QEMU's
VFIO passthrough so I am asking the following design question before trying to
write and push code.
After SR-IOV being enabled on this hardware
On Monday 03 June 2013 10:35:28 Jordan Justen wrote:
This should be fixed by Xiao's fix double free the memslot in
kvm_set_phys_mem patch.
Confirmed, with this one-liner patch the bug is gone.
On Mon, Jun 3, 2013 at 10:23 AM, Peter Wu lekenst...@gmail.com wrote:
Hi,
With the current git
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
QEMU models two (of the three) ACMD41 has two modes, inquiry and
first. The selection logic for which of the two is incorrect - it
compares != 0 for the entire argument value rather than only bits 23:0
as per the spec. Fix.
Signed-off-by:
Applied. Thanks.
Regards,
Anthony Liguori
On Sunday, June 2, 2013 9:37:55 PM CDT, Steven.G wrote:
Dear all,
I've a scene,
I have many host nodes with linux kernels, and I want to boot one guest
OS on all these nodes use QEMU/KVM. In order that I can use all the
physical CPUs and Mems distributed on these linux nodes, and the Guest
On 06/03/13 14:42, Michael Tokarev wrote:
03.06.2013 16:34, Eric Blake wrote:
On 06/03/2013 03:20 AM, Michael Tokarev wrote:
Initially the code ensured that we have exactly one of data= or file=
option for -acpitable. But after some transformations, the condition
becomes
if (has_data ==
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
The QSPI controller was using byte-wide stripes when striping across
the two flashes in dual parallel mode. The real hardware however uses
individual bit striping. QEMU misbehaves in the (corner) case where
data is written/read in dual-parallel
Stefano Stabellini stefano.stabell...@eu.citrix.com writes:
Anthony,
please pull the following changes since commit
6a4e17711442849bf2cc731ccddef5a2a2d92d29:
On 06/03/2013 02:02 PM, Alex Williamson wrote:
On Mon, 2013-06-03 at 18:33 +0200, Benoît Canet wrote:
Hello,
I plan to write a PF driver for an SR-IOV card and make the VFs work with QEMU's
VFIO passthrough so I am asking the following design question before trying to
write and push code.
On 06/01/2013 08:13 AM, Benoît Canet wrote:
Hello,
I may have soon the PF driver of an SR-IOV card to code and make work with
QEMU/KVM so I have the following questions.
In an AMD64 setup where QEMU use VFIO to passthrough the VFs of an SR-IOV card
to a guest will the consequences of a PF FLR
Peter Wu lekenst...@gmail.com writes:
Hi,
With the current git source (f10acc8b38d65a66ffa0588a036489d7fa6a593e),
`qemu-system-x86_64 -enable-kvm` fails to run with the following error:
kvm_set_phys_mem: error unregistering overlapping slot: Invalid argument
After this message, qemu
On Mon, 2013-06-03 at 14:34 -0400, Don Dutile wrote:
On 06/03/2013 02:02 PM, Alex Williamson wrote:
On Mon, 2013-06-03 at 18:33 +0200, Benoît Canet wrote:
Hello,
I plan to write a PF driver for an SR-IOV card and make the VFs work with
QEMU's
VFIO passthrough so I am asking the
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
Make SPI and QSPI different classes. QSPIPS is setup as a child of SPIPS.
Only QSPI has the LQSPI functionality, so move all that to the child class.
Signed-off-by: Peter Crosthwaite peter.crosthwa...@xilinx.com
Reviewed-by: Peter Maydell
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
This message was printing out the data in decimal only, which is not
very friendly to the debugging developer. Add hex variant in
parenthesis to make it consistent with other similar messages in this
module.
Signed-off-by: Peter Crosthwaite
Luiz Capitulino lcapitul...@redhat.com writes:
Hi,
This is an small update on QMP/HMP/QAPI mainternership. Please, check
individual patches for details.
Acked-by: Anthony Liguori aligu...@us.ibm.com
Regards,
Anthony Liguori
Luiz Capitulino (2):
MAINTAINERS: new maintainers for
Il 03/06/2013 19:17, Luiz Capitulino ha scritto:
This entry doesn't reflect reality for a few years now. This commit
splits it into Human Monitor (HMP), QAPI and QMP. Markus is dropped
as a maintainer.
This is what we have been for the last few years. Also, it's going
to help me to offload
to a guest will the consequences of a PF FLR be handled fine by QEMU and the
guest ?
the reset occurs long before the device is passed to the guest.
I was asking this because the PF driver should reset the PF while the VF are
used by VFIO/QEMU when the PF doesn't respond anymore.
The PF
On Mon, 03 Jun 2013 21:13:30 +0200
Paolo Bonzini pbonz...@redhat.com wrote:
Il 03/06/2013 19:17, Luiz Capitulino ha scritto:
This entry doesn't reflect reality for a few years now. This commit
splits it into Human Monitor (HMP), QAPI and QMP. Markus is dropped
as a maintainer.
This is
Hello,
For guest sizes = 1TB RAM the guest OS is unable to boot up (please
see attached GIF file for the Oops message). Wonder if this is a
bug/regression in qemu/seabios or does one have to enable/disable
something else in the qemu command line (pl. see below) ?
Thanks
Vinod
Host and
On Mon, Jun 03, 2013 at 03:54:48PM -0400, Luiz Capitulino wrote:
On Mon, 03 Jun 2013 21:13:30 +0200
Paolo Bonzini pbonz...@redhat.com wrote:
Il 03/06/2013 19:17, Luiz Capitulino ha scritto:
This entry doesn't reflect reality for a few years now. This commit
splits it into Human Monitor
101 - 200 of 246 matches
Mail list logo
