> 1. some other tbs being invalidated.
> 2. interrrupt pending
Could you point out "interrrupt pending" means where? I'd like to take a look,
thanks. :)
Regards,
chenwj
--
Wei-Ren Chen (陳韋任)
Computer Systems Lab, Institute of Information Science,
Academia Sinica, Taiwan (R.O.C.)
Tel:886-2-278
On 13 December 2011 06:19, Paul Brook wrote:
>> > When compiling qemu statically with multilib on PPC, we hit the
>> > same issue that commit 845f2c2812d9ed24b36c02a3d06ee83aeafe8b49
>> > is fixing. Do the same here.
>>
>> How many of these ld files can we get rid of if we use -Ttext-segment
>> in
On Tue, Dec 13, 2011 at 12:22:57PM +1100, mich...@ellerman.id.au wrote:
> We'd like to get the progname for help output, so add an accessor.
>
> Signed-off-by: Michael Ellerman
> ---
> qemu-error.c |5 +
> qemu-error.h |1 +
> 2 files changed, 6 insertions(+), 0 deletions(-)
Both pa
On Mon, Dec 12, 2011 at 08:50:39PM -0600, Erik Lotspeich wrote:
> Hi,
>
> I posted this on qemu-discuss and didn't receive any replies; sorry
> for posting it twice.
>
> I have OpenSUSE 12.1 and I have a 64-bit Windows 7 VM that recognizes
> the emulated ICH6 sound (HDA audio device). Although W
On Mon, Dec 12, 2011 at 11:53:28AM -0600, Anthony Liguori wrote:
> On 12/12/2011 11:22 AM, Alon Levy wrote:
> >On Mon, Dec 12, 2011 at 10:24:53AM -0600, Anthony Liguori wrote:
> >>On 12/12/2011 10:00 AM, Alon Levy wrote:
> >>>On Mon, Dec 12, 2011 at 03:23:35PM +, Stefan Hajnoczi wrote:
> On
At 12/13/2011 02:01 PM, HATAYAMA Daisuke Write:
> From: Wen Congyang
> Subject: Re: [Qemu-devel] [RFC][PATCT 0/5 v2] dump memory when host pci
> device is used by guest
> Date: Tue, 13 Dec 2011 11:35:53 +0800
>
>> Hi, hatayama-san
>>
>> At 12/13/2011 11:12 AM, HATAYAMA Daisuke Write:
>>> Hello W
Am 09.12.2011 15:25, schrieb Anthony Liguori:
> On 12/09/2011 08:04 AM, Kevin Wolf wrote:
>> Am 09.12.2011 14:08, schrieb Anthony Liguori:
>>> On 12/09/2011 05:26 AM, Kevin Wolf wrote:
Am 02.12.2011 21:20, schrieb Anthony Liguori:
> This really shows the power of dynamic object properties
Hi,
> Now I understand that for dynamically created properties (like on your
> PCB) this is necessary and can't be avoided. For about 99% of the
> devices static definition of properties would be enough, though.
>
> So basically what I'm asking for is getting the static structs back for
> the 9
Am 13.12.2011 09:03, schrieb Stefan Hajnoczi:
> On Tue, Dec 13, 2011 at 12:22:57PM +1100, mich...@ellerman.id.au wrote:
>> We'd like to get the progname for help output, so add an accessor.
>>
>> Signed-off-by: Michael Ellerman
>> ---
>> qemu-error.c |5 +
>> qemu-error.h |1 +
>> 2 f
Hi,
> We aren't breaking an ABI here. libvirt can detect that this command is
> gone and probe for the new command.
Please stop this. There are libvirt versions in the wild which can't
deal with this and thus will break, no matter how hard you try to wave
it away. The question is not wheneve
On 12 December 2011 06:43, Evgeny Voevodin wrote:
> This set of patches adds support for Samsung S5PC210-based boards NURI and
> SMDKC210.
> Tested on Linux kernel v3.x series. Usage of "-smp 2" option is reuired for
> now.
General question -- is there publicly available hardware documentation
Dear Peter,
Public Exynos4210 UM is available at
http://www.samsung.com/global/system/business/semiconductor/product/2011/12/2/738994Pulbicmanual_Exynos4210_Ver1.pdf
Thanks,
Dmitry Solodkiy,
Mobile SW PL, Advanced Software Group,
Moscow R&D center, Samsung Electronics
---
On 12 December 2011 06:43, Evgeny Voevodin wrote:
>
> Signed-off-by: Evgeny Voevodin
> ---
> Makefile.target | 2 +-
> hw/exynos4210.c | 12 ++
> hw/exynos4210_pwm.c | 433
> +++
> 3 files changed, 446 insertions(+), 1 deletions(-)
>
From: Alex Rozenman
This fixes a common bug with initial region_offset value.
Usually, the pages are re-assigned afterwards, so the bug
has a very small effect on regular QEMU use flows.
Signed-off-by: Alex Rozenman
---
exec.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff
On 13 December 2011 10:37, Dmitry Solodkiy wrote:
> Dear Peter,
>
> Public Exynos4210 UM is available at
> http://www.samsung.com/global/system/business/semiconductor/product/2011/12/2/738994Pulbicmanual_Exynos4210_Ver1.pdf
Thanks. It seems to be missing some info though -- for example
you
On 12/12/2011 06:26 PM, Anthony Liguori wrote:
>
> Nope, it has to be dropped.
>
> Commands using CMD_ASYNC may fail in arbitrary ways because of the way
> error reporting is done. This is an unfixable problem until we
> eliminate all uses of qerror_report().
>
Why don't we eliminate all uses for
Hi,
>> Two possible ideas:
>> 1. Pass the value in from qemu
> Do you mean to create the 64bit region dynamically? I've tried to obtain
> RAM size somehow inside DSL code, but the ACPI spec doesn't tell how to
> do that.
There is a global variable IIRC. You could also check the e820 table
pass
On 12 December 2011 06:43, Evgeny Voevodin wrote:
> Secondary CPU bootloader enables interrupt and issues wfi until start address
> is written to system controller. The position where to find this start
> address is hardcoded to 0x1030. This commit adds new bootloader for
> secondary CPU which
On Mon, Dec 12, 2011 at 7:36 PM, Anthony Liguori wrote:
> I choose the serial device to showcase what we'll eventually be able to do.
> The three relevant files are:
>
> https://github.com/aliguori/qemu/blob/qom-next/hw/isa-serial.c
>
> https://github.com/aliguori/qemu/blob/qom-next/hw/mm-serial.
On Mon, 12 Dec 2011, Stefano Stabellini wrote:
> > Really, I think this is something inherently incompatible with the
> > current memory API. If Xen has this unfixable special "requirement"
> > (it's rather a design issue IMHO), adjust the API and adapt all devices.
> > Hot-fixing only a single one
On 12 December 2011 06:43, Evgeny Voevodin wrote:
>
> Signed-off-by: Evgeny Voevodin
> ---
> hw/devices.h | 2 +-
> hw/lan9118.c | 115
> ++
> 2 files changed, 109 insertions(+), 8 deletions(-)
>
> diff --git a/hw/devices.h b/hw/device
On 12 December 2011 06:43, Evgeny Voevodin wrote:
> SMDKC210 uses lan9215 chip, but lan9118 in 16-bit mode seems to
> be enough.
>
> Signed-off-by: Evgeny Voevodin
> ---
> hw/exynos4210.c | 18 ++
> 1 files changed, 18 insertions(+), 0 deletions(-)
>
> diff --git a/hw/exynos421
On Mon, 12 Dec 2011 17:38:36 -0600
Michael Roth wrote:
> On 12/12/2011 05:03 PM, Anthony Liguori wrote:
> > On 12/07/2011 10:33 AM, Adam Litke wrote:
> >> Currently the make variable qapi-dir refers to the qapi-generated
> >> directory in
> >> absolute terms. This causes the harmless but ugly mak
On Tue, 13 Dec 2011 12:40:51 +0900
Isaku Yamahata wrote:
> The variable is deleted by 1bcef683bf840a928d633755031ac572d5fdb851
> So remove its declaration.
>
> Cc: Luiz Capitulino
> Signed-off-by: Isaku Yamahata
Acked-by: Luiz Capitulino
> ---
> migration.h |2 --
> 1 files changed, 0 i
On 2011-12-13 12:55, Stefano Stabellini wrote:
> On Mon, 12 Dec 2011, Stefano Stabellini wrote:
>>> Really, I think this is something inherently incompatible with the
>>> current memory API. If Xen has this unfixable special "requirement"
>>> (it's rather a design issue IMHO), adjust the API and ad
Running with mismatched host and guest logical block sizes is going
to become more important as 4k-sector disks become more widespread.
This is because we need a 512 byte disk to boot from.
Mismatched block sizes have two problems:
1) with cache=none or with non-raw protocols, you just cannot do
The BDRV_O_SNAPSHOT flag is stored in open_flags but not passed to
bdrv_open. This makes the usage of bs->open_flags wrong in
bdrv_snapshot_goto.
(Instead, bdrv_commit uses the backing file's open_flags and those
flags never include any of BDRV_O_SNAPSHOT, BDRV_O_NO_BACKING
or BDRV_O_RDWR).
We w
When emulating small logical block sizes, the only overlaps
that matter are at host block size granularity, not cluster.
Make wait_for_overlapping_requests more flexible in this
respect, too.
Signed-off-by: Paolo Bonzini
---
block.c | 43 ---
1 files cha
When the guest sees a higher alignment than the host, writes may be
done in multiple steps. So, reads have to be serialized against
overlapping writes, so that the writes look atomic to the guest.
This is true even when O_DIRECT is not in use.
Signed-off-by: Paolo Bonzini
---
block.c | 22 +++
When the guest sees a lower alignment than the host, and O_DIRECT
is in place, I/O might not span an integer number of host sectors.
If this is the case, add a few sectors at the beginning and the end.
When reading, copy interesting data from there to the guest buffer.
When writing, merge data fro
On 12/13/2011 12:45 AM, Stefan Weil wrote:
Am 12.12.2011 20:12, schrieb Stefan Berger:
The following series of patches adds TPM (Trusted Platform Module)
support
to Qemu. An emulator for the TIS (TPM Interface Spec) interface is
added that provides the basis for accessing a 'backend' implementi
On Windows, cpus.c needs access to the hThread. Add a Windows-specific
function to grab it. This requires changing the CPU threads to
joinable. There is no substantial change because the threads run
in an infinite loop.
Signed-off-by: Paolo Bonzini
---
cpu-defs.h |9 +
cp
Am 12.12.2011 16:58, schrieb Paul Brook:
>>> Trying to make a 32-bit target "64-bit safe" without actually
>>> implementing the 64-bit target is a complete waste of time.
>>
>> That's where we disagree. I rather do things right from the start than
>> leaving the cleanup work to someone else later o
On 12/12/2011 11:51 PM, Paul Brook wrote:
+tpm_passthrough="no"
Same as before, please probe for existence.
We would be probing for /dev/tpm0. Is that really what we want that this
driver only gets compiled if /dev/tpm0 is (currently) available?
If what you say is true then this code should al
Use ioctls if possible, else see what alignment it takes for O_DIRECT
to succeed.
Signed-off-by: Paolo Bonzini
---
block/raw-posix.c | 72
block/raw-win32.c | 42 +++
2 files changed, 97 insertions(+), 17 deleti
On Tue, Dec 13, 2011 at 2:06 AM, Stefan Hajnoczi wrote:
> Please post your QEMU command-line (you can find it with "ps aux | grep
> qemu").
>
> If you are running through libvirt/virsh/virt-manager there may be
> permission requirements since the guest can be set to run as an
> unprivileged user w
On 2011-12-09 08:57, Wen Congyang wrote:
> Hi, all
>
> 'virsh dump' can not work when host pci device is used by guest. We have
> discussed this issue here:
> http://lists.nongnu.org/archive/html/qemu-devel/2011-10/msg00736.html
>
> We have determined to introduce a new command dump to dump memor
The passed flags are changed slightly before passing them to bdrv_open.
Store the same flags in bs->open_flags, so that they are used correctly
in bdrv_snapshot_goto. In addition, this way we will be able to query
them and get back consistent values.
Signed-off-by: Paolo Bonzini
---
block.c |
The iSCSI backend already gets the block size from the READ CAPACITY
command it sends. Save it so that the generic block layer gets it
too.
Signed-off-by: Paolo Bonzini
---
block/iscsi.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/block/iscsi.c b/block/iscsi.c
index
On 2011-12-09 09:06, Wen Congyang wrote:
> The memory mapping list stores virtual address and physical address mapping.
> The folloing patch will use this information to create PT_LOAD in the vmcore.
>
> Signed-off-by: Wen Congyang
> ---
> Makefile.target |1 +
> memory_mapping.c | 130
>
Signed-off-by: Paolo Bonzini
---
block.c |4 +++-
block_int.h |3 +++
2 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/block.c b/block.c
index 9e8ffb8..91622db 100644
--- a/block.c
+++ b/block.c
@@ -588,6 +588,7 @@ static int bdrv_open_common(BlockDriverState *bs, const
The alignment field is now set to the value that is promised by the guest,
rather than required by the host. The next patches will make QEMU aware
of the host-provided values, so make this clear.
Signed-off-by: Paolo Bonzini
---
block.c | 10 +-
block.h |2 +-
Am 12.12.2011 16:58, schrieb Paul Brook:
>> For me the most annoying issue was that tcg_gen_qemu_{ld,st}* needs TCGv.
>
> You mean the value transferred is always TCGv sized, so ld32u requires an
> additional truncation before doing 32-bit arithmetic? Fixing that is
> completely independent of
Non-raw protocols never cache their data. Make this visible by setting
BDRV_O_NOCACHE in the open_flags. It will be used to handle block sizes
smaller than the backend's block size.
Signed-off-by: Paolo Bonzini
---
block/curl.c |1 +
block/iscsi.c|1 +
block/nbd.c |1 +
Signed-off-by: Paolo Bonzini
---
block_int.h | 17 -
1 files changed, 8 insertions(+), 9 deletions(-)
diff --git a/block_int.h b/block_int.h
index f846f90..9324866 100644
--- a/block_int.h
+++ b/block_int.h
@@ -192,15 +192,18 @@ struct BlockDriver {
struct BlockDriverState {
Make it possible to test the alignment code using qemu-io.
Signed-off-by: Paolo Bonzini
---
qemu-io.c | 33 -
1 files changed, 28 insertions(+), 5 deletions(-)
diff --git a/qemu-io.c b/qemu-io.c
index ffa62fb..f866eb3 100644
--- a/qemu-io.c
+++ b/qemu-io.c
@@ -
On 12/12/2011 10:47 PM, Paul Brook wrote:
The full set of devices names and properties used in this example are
below:
Type: I440FX
Is-a: Device
Implements: PciBus
Name: i440fx
Properties:
piix3: Composition
slot[1.0]: Backlink
Type: PIIX3
Isa-a: PciDevice
Implem
In the next patches, the protocols will modify bs->open_flags to signify
that they cannot support the exact requested feature set. Pass the
modified flags to the format.
Signed-off-by: Paolo Bonzini
---
block.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/block.c b
This duplicates a bit in open_flags, we do not need it.
Signed-off-by: Paolo Bonzini
---
block.c |3 +--
block_int.h |3 ---
2 files changed, 1 insertions(+), 5 deletions(-)
diff --git a/block.c b/block.c
index 6734e66..4cf441b 100644
--- a/block.c
+++ b/block.c
@@ -604,7 +604,6 @@
On 12/13/2011 03:27 AM, Kevin Wolf wrote:
Am 09.12.2011 15:25, schrieb Anthony Liguori:
On 12/09/2011 08:04 AM, Kevin Wolf wrote:
Am 09.12.2011 14:08, schrieb Anthony Liguori:
On 12/09/2011 05:26 AM, Kevin Wolf wrote:
Am 02.12.2011 21:20, schrieb Anthony Liguori:
This really shows the power
On 12/13/2011 03:48 AM, Gerd Hoffmann wrote:
Hi,
Now I understand that for dynamically created properties (like on your
PCB) this is necessary and can't be avoided. For about 99% of the
devices static definition of properties would be enough, though.
So basically what I'm asking for is gett
To implement mismatching block size, we will reuse the request tracking
mechanism that is used for copy-on-read. However, waiting for overlapping
reads is not needed to protect against "torn reads", so add a flag to
wait_for_overlapping_requests.
Signed-off-by: Paolo Bonzini
---
block.c | 13
On 12/13/11 02:22, m...@linux.vnet.ibm.com wrote:
> When testing ipod on QEMU by He Jie Xu,qemu made a
> assertion.
> We found that the ipod with 2 configurations,and the usb-linux did not parse
> the descriptor correctly.
> The descr_len returned is the total length of the all configurations,not
On 12/13/2011 03:03 AM, Alon Levy wrote:
On Mon, Dec 12, 2011 at 11:53:28AM -0600, Anthony Liguori wrote:
On 12/12/2011 11:22 AM, Alon Levy wrote:
On Mon, Dec 12, 2011 at 10:24:53AM -0600, Anthony Liguori wrote:
On 12/12/2011 10:00 AM, Alon Levy wrote:
On Mon, Dec 12, 2011 at 03:23:35PM +
On 12/13/2011 05:06 AM, Avi Kivity wrote:
On 12/12/2011 06:26 PM, Anthony Liguori wrote:
Nope, it has to be dropped.
Commands using CMD_ASYNC may fail in arbitrary ways because of the way
error reporting is done. This is an unfixable problem until we
eliminate all uses of qerror_report().
On 12/13/2011 05:35 AM, Stefan Hajnoczi wrote:
On Mon, Dec 12, 2011 at 7:36 PM, Anthony Liguori wrote:
I choose the serial device to showcase what we'll eventually be able to do.
The three relevant files are:
https://github.com/aliguori/qemu/blob/qom-next/hw/isa-serial.c
https://github.com/
Am 13.12.2011 14:31, schrieb Anthony Liguori:
> On 12/13/2011 03:27 AM, Kevin Wolf wrote:
>> Am 09.12.2011 15:25, schrieb Anthony Liguori:
>>> On 12/09/2011 08:04 AM, Kevin Wolf wrote:
Am 09.12.2011 14:08, schrieb Anthony Liguori:
> On 12/09/2011 05:26 AM, Kevin Wolf wrote:
>> Am 02.12
This has been dead since the removal of synchronous I/O callbacks.
Signed-off-by: Paolo Bonzini
---
block/raw-posix.c | 25 +++--
1 files changed, 3 insertions(+), 22 deletions(-)
diff --git a/block/raw-posix.c b/block/raw-posix.c
index 2ee5d69..007d1d3 100644
--- a/block/
On Tue, Dec 13, 2011 at 07:51:17AM -0500, Stefan Berger wrote:
> On 12/12/2011 11:51 PM, Paul Brook wrote:
> +tpm_passthrough="no"
> >>>Same as before, please probe for existence.
> >>We would be probing for /dev/tpm0. Is that really what we want that this
> >>driver only gets compiled if /dev/
Hopefully, this will help operating systems and they will make less
misaligned I/O operations. Or on Linux, at least fdisk will tell the
user that they should try and align partitions.
Signed-off-by: Paolo Bonzini
---
block.c | 17 +
block.h | 15 ++-
2 files cha
This series adds the 'block_stream' command which copies the contents of a
backing file into the image file while the VM is running. The series builds on
copy-on-read and zero detection features which I sent out recently and I
suggest grabbing my git tree to try it out without merging these depend
Signed-off-by: Stefan Hajnoczi
---
Makefile.objs |2 +-
qemu-coroutine-sleep.c | 38 ++
qemu-coroutine.h |6 ++
3 files changed, 45 insertions(+), 1 deletions(-)
create mode 100644 qemu-coroutine-sleep.c
diff --git a/Makefile.objs
Add query-block-jobs, which shows the progress of ongoing block device
operations.
Signed-off-by: Stefan Hajnoczi
---
blockdev.c | 33 +
hmp.c| 40
hmp.h|1 +
monitor.c|7 ++
Add block_job_set_speed, which sets the maximum speed for a background
block operation.
Signed-off-by: Stefan Hajnoczi
---
blockdev.c | 25 +
hmp-commands.hx | 14 ++
hmp.c| 14 ++
hmp.h|1 +
qapi-schema.jso
Add the block_stream command, which starts copy backing file contents
into the image file. Later patches add control over the background copy
speed, cancelation, and querying running streaming operations.
Signed-off-by: Stefan Hajnoczi
---
blockdev.c | 68 +++
This patch implements rate-limiting for image streaming. If we've
exceeded the bandwidth quota for a 100 ms time slice we sleep the
coroutine until the next slice begins.
Signed-off-by: Stefan Hajnoczi
---
block/stream.c | 65 ++-
1 files ch
Signed-off-by: Stefan Hajnoczi
---
Makefile.objs |1 +
block/stream.c | 121
block_int.h|3 +
trace-events |4 ++
4 files changed, 129 insertions(+), 0 deletions(-)
create mode 100644 block/stream.c
diff --git a/Makefi
Signed-off-by: Stefan Hajnoczi
---
block_int.h | 83 +++
1 files changed, 83 insertions(+), 0 deletions(-)
diff --git a/block_int.h b/block_int.h
index 89a860c..bc397c4 100644
--- a/block_int.h
+++ b/block_int.h
@@ -69,6 +69,36 @@ typedef
Add block_job_cancel, which stops an active block streaming operation.
Signed-off-by: Stefan Hajnoczi
---
blockdev.c | 19 ++-
hmp-commands.hx | 14 ++
hmp.c| 13 +
hmp.h|1 +
monitor.c|3 +++
monitor.h
On Tue, 13 Dec 2011, Jan Kiszka wrote:
> On 2011-12-13 12:55, Stefano Stabellini wrote:
> > On Mon, 12 Dec 2011, Stefano Stabellini wrote:
> >>> Really, I think this is something inherently incompatible with the
> >>> current memory API. If Xen has this unfixable special "requirement"
> >>> (it's r
hi stefan:
all these patches looks good to me except one thing,
when I run a "qemu-img commit" command,
seems entire image(from start to end sector) will be write to the backing file,
I think what we really need is to commit only dirty sectors.
also maybe we can use a writeback mechanism alternaiv
python test-stream.py
Signed-off-by: Stefan Hajnoczi
---
test-stream.py | 208
1 files changed, 208 insertions(+), 0 deletions(-)
create mode 100644 test-stream.py
diff --git a/test-stream.py b/test-stream.py
new file mode 100644
index
On Tue, Dec 13, 2011 at 01:52:25PM +, Stefan Hajnoczi wrote:
> Signed-off-by: Stefan Hajnoczi
> ---
> Makefile.objs |1 +
> block/stream.c | 121
>
> block_int.h|3 +
> trace-events |4 ++
> 4 files changed, 129 ins
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/882997/+attachment/2631363/+files/Lspci.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/882997
Title:
64-bi
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/882997/+attachment/2631366/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/882997
T
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/882997/+attachment/2631370/+files/UdevDb.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/882997
Title:
64-
apport information
** Attachment added: "RelatedPackageVersions.txt"
https://bugs.launchpad.net/bugs/882997/+attachment/2631369/+files/RelatedPackageVersions.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launch
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/882997/+attachment/2631368/+files/ProcModules.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/882997
T
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/882997/+attachment/2631365/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/882997
T
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/882997/+attachment/2631361/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/882997
From: Stefan Hajnoczi
The v9fs_read() and v9fs_write() functions rely on iovec[] manipulation
code should be replaced with QEMUIOVector to avoid duplicating code.
In the future it may be possible to make the code even more concise by
using QEMUIOVector consistently across virtio and 9pfs.
The "v
From: "Aneesh Kumar K.V"
Signed-off-by: Aneesh Kumar K.V
---
fsdev/file-op-9p.h |2 +-
hw/9pfs/virtio-9p.c | 21 +++--
hw/9pfs/virtio-9p.h |2 +-
trace-events|8
4 files changed, 17 insertions(+), 16 deletions(-)
diff --git a/fsdev/file-op-9p.h b
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/882997/+attachment/2631362/+files/Dependencies.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/882997
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/882997/+attachment/2631367/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/882
On Tue, Dec 13, 2011 at 10:23:18AM -0200, Luiz Capitulino wrote:
> On Mon, 12 Dec 2011 17:38:36 -0600
> Michael Roth wrote:
>
> > On 12/12/2011 05:03 PM, Anthony Liguori wrote:
> > > On 12/07/2011 10:33 AM, Adam Litke wrote:
> > >> Currently the make variable qapi-dir refers to the qapi-generated
On 12/13/2011 03:36 PM, Anthony Liguori wrote:
> On 12/13/2011 05:06 AM, Avi Kivity wrote:
>> On 12/12/2011 06:26 PM, Anthony Liguori wrote:
>>>
>>> Nope, it has to be dropped.
>>>
>>> Commands using CMD_ASYNC may fail in arbitrary ways because of the way
>>> error reporting is done. This is an un
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/882997/+attachment/2631371/+files/UdevLog.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/882997
Title:
6
On Tue, Dec 13, 2011 at 12:55 PM, Erik Lotspeich
wrote:
> On Tue, Dec 13, 2011 at 2:06 AM, Stefan Hajnoczi wrote:
>> Please post your QEMU command-line (you can find it with "ps aux | grep
>> qemu").
>>
>> If you are running through libvirt/virsh/virt-manager there may be
>> permission requiremen
On 12 December 2011 06:43, Evgeny Voevodin wrote:
> --- /dev/null
> +++ b/hw/exynos4210_sdhc.c
> @@ -0,0 +1,1666 @@
> +/*
> + * Samsung exynos4210 SD/MMC host controller
> + * (SD host controller specification ver. 2.0 compliant)
Is there anything in this implementation which is exynos specific,
apport information
** Description changed:
Host: Ubuntu 11.10 kernel vmlinuz-3.0.0-12-generic or vmlinuz-3.0.0-12-server
on AMD Athlon(tm) II P360 Dual-Core
Guests: SLES 10 or 11, all 64 bit
32 bit windows guest starts fine. All 64 bit linux guests loop during
boot, when GRUB is start
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/882997/+attachment/2631364/+files/Lsusb.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/882997
Title:
64-bi
Am 13.12.2011 14:43, schrieb Anthony Liguori:
> On 12/13/2011 05:35 AM, Stefan Hajnoczi wrote:
>> On Mon, Dec 12, 2011 at 7:36 PM, Anthony Liguori
>> wrote:
>>> I choose the serial device to showcase what we'll eventually be able to do.
>>> The three relevant files are:
>>>
>>> https://github.c
On 12 December 2011 06:43, Evgeny Voevodin wrote:
> From: Mitsyanko Igor
>
> Data transfer direction between host controller and SD/MMC card is selected by
> host controller configuration registers, but whether we actually need or need
> not perform data transfer depends on type of last issued co
On Tue, Dec 13, 2011 at 2:12 PM, Yibin Shen wrote:
> all these patches looks good to me except one thing,
> when I run a "qemu-img commit" command,
> seems entire image(from start to end sector) will be write to the backing
> file,
> I think what we really need is to commit only dirty sectors.
>
On Tue, Dec 13, 2011 at 2:14 PM, Marcelo Tosatti wrote:
> On Tue, Dec 13, 2011 at 01:52:25PM +, Stefan Hajnoczi wrote:
>> Signed-off-by: Stefan Hajnoczi
>> ---
>> Makefile.objs | 1 +
>> block/stream.c | 121
>>
>> block_int.h
On Tue, Dec 13, 2011 at 2:37 PM, Aneesh Kumar K.V
wrote:
> This change avoids a possible iovec[] buffer overflow when indirect
> vrings are used since the number of vectors is now limited by the
> underlying VirtQueueElement and cannot be out-of-bounds.
Please consider both of these patches for s
Thank you - I overlooked the obvious.
Regards,
Erik
On Tue, Dec 13, 2011 at 8:57 AM, Stefan Hajnoczi wrote:
> On Tue, Dec 13, 2011 at 12:55 PM, Erik Lotspeich
> wrote:
>> On Tue, Dec 13, 2011 at 2:06 AM, Stefan Hajnoczi wrote:
>>> Please post your QEMU command-line (you can find it with "ps a
On 12/13/2011 08:33 AM, Adam Litke wrote:
On Tue, Dec 13, 2011 at 10:23:18AM -0200, Luiz Capitulino wrote:
On Mon, 12 Dec 2011 17:38:36 -0600
Michael Roth wrote:
On 12/12/2011 05:03 PM, Anthony Liguori wrote:
On 12/07/2011 10:33 AM, Adam Litke wrote:
Currently the make variable qapi-dir ref
Hi
- monitor command async framework
* how to merge async command?
- merge all QAPI (will take until the end of the release)
- let things as they are
- use a new corroutine for each async command, so the error can be
maintained on each corrutine.
* currently only one async c
On 12/13/2011 04:22 PM, Erik Lotspeich wrote:
Thank you - I overlooked the obvious.
Actually it may be a distro bug, I suggest you report it there.
Paolo
1 - 100 of 160 matches
Mail list logo
