From: Dmitry Fleytman
Virtio-net driver currently negotiates network offloads
on startup via features mechanism and have no ability to
disable and re-enable offloads later.
This patch introduced a new control command that allows
to configure device network offloads state dynamically.
The patch al
From: Dmitry Fleytman
This patch implements recently accepted by virtio-spec
dynamic offloads configuration feature.
See commit message for details.
V4 changes:
1. Feature definitions re-used for command bitmask
2. Command data made uint64
3. Commit messsages fixed
Reported-by: Rusty Russ
Please ignore this message
The debug printfs on every page program/read is extremely verbose. Add
a second level of debug for this.
Signed-off-by: Peter Crosthwaite
---
hw/m25p80.c | 40 +---
1 files changed, 21 insertions(+), 19 deletions(-)
diff --git a/hw/m25p80.c b/hw/m25p80.c
i
If there is no backing bdrv, let the debugging developer know about it.
Signed-off-by: Peter Crosthwaite
---
hw/m25p80.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/hw/m25p80.c b/hw/m25p80.c
index d853a2e..efcc7f4 100644
--- a/hw/m25p80.c
+++ b/hw/m25p80.c
@@ -606,6
Hi, Kevin
Except the comments from Eric for better code comments, do you think
other things need improved? Modified patches is addressed as following,
I hope fix all in next version, to avoid using more time of reviewer.
>
> v11:
>General change:
>5/17: check if snapshot > 0 on success
Some of the debug printfs in m25p80 are really guest errors.
Changed over to qemu_log_mask(LOG_GUEST_ERROR accordingly.
Signed-off-by: Peter Crosthwaite
---
hw/m25p80.c | 12 +++-
1 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/hw/m25p80.c b/hw/m25p80.c
index c395e98..4
Some dodgy casts were making a mess of these msgs.
Signed-off-by: Peter Crosthwaite
---
Remove misleading "k" suffix from erase size message
Use PRIxN macros where appropriate (Edgar review)
hw/m25p80.c | 13 +++--
1 files changed, 7 insertions(+), 6 deletions(-)
diff --git a/hw/m25p
Fix up the debug printfery m25p80 in various ways. 0 functional diff.
Peter Crosthwaite (4):
m25p80: Fix debug messages.
m25p80: Convert guest errors to LOG_GUEST_ERROR
m25p80.c: Multiple debug verbosity levels
m25p80: Add debug message for no bdrv
hw/m25p80.c | 52 +++
Hi Edgar,
On Wed, Apr 3, 2013 at 4:50 PM, Edgar E. Iglesias
wrote:
> On Wed, Apr 03, 2013 at 02:09:16PM +1000, Peter Crosthwaite wrote:
>> Some dodgy casts were making a mess of these msgs.
>
>
> Hi Peter
>
>>
>> Signed-off-by: Peter Crosthwaite
>> ---
>>
>> hw/m25p80.c |6 +++---
>> 1 file
Modify Anthony's starvation detection logic to keep the BQL unlocked
until the starvation condition goes away. Otherwise the counter has to
count up to 1000 for each needed iteration until the busy-wait is
lifted.
Reset the counter back to zero once glib_pollfds_fill returns with a
non-zero timout
Hi Anthony,
On Fri, Apr 5, 2013 at 11:46 PM, Anthony Liguori wrote:
> The char-flow refactoring introduced a busy-wait that depended on
> an action from the VCPU thread. However, the VCPU thread could
> never take that action because the busy-wait starved the VCPU thread
> of the BQL because it
Hi Paolo,
On Sat, Apr 6, 2013 at 1:59 AM, Paolo Bonzini wrote:
> The character backend refactoring introduced an undesirable busy wait.
> The busy wait happens if can_read returns zero and there is data available
> on the character device's file descriptor. Then, the I/O watch will
> fire contin
>> I start a kvm VM with vnc(using the zrle protocol) connect, sometimes qemu
>> program crashed during starting period, received signal SIGABRT.
>> Trying about 20 times, this crash may be reproduced.
>> I guess the cause memory corruption or double free.
>
> Which version of QEMU are you running
On Sat, Apr 06, 2013 at 10:12:49PM +0200, Alexander Graf wrote:
>
> On 06.04.2013, at 22:07, Edgar E. Iglesias wrote:
>
> > On Sat, Apr 06, 2013 at 01:38:52PM +0200, Alexander Graf wrote:
> >>
> >> On 06.04.2013, at 13:27, Peter Maydell wrote:
> >>
> >>> On 6 April 2013 10:07, Alexander Graf w
Ping? Does anybody with a PPC MacOS (10.3 or better) have time to
test these patches?
(C.W.: I cc'd you since you submitted a macos patch recently so
I figured you might be interested.)
Patchwork urls:
http://patchwork.ozlabs.org/patch/231004/
http://patchwork.ozlabs.org/patch/231006/
http://patc
On 06.04.2013, at 22:07, Edgar E. Iglesias wrote:
> On Sat, Apr 06, 2013 at 01:38:52PM +0200, Alexander Graf wrote:
>>
>> On 06.04.2013, at 13:27, Peter Maydell wrote:
>>
>>> On 6 April 2013 10:07, Alexander Graf wrote:
On ARM, look at highbank. Because we're not running we're lacking
>>>
On Sat, Apr 06, 2013 at 01:38:52PM +0200, Alexander Graf wrote:
>
> On 06.04.2013, at 13:27, Peter Maydell wrote:
>
> > On 6 April 2013 10:07, Alexander Graf wrote:
> >> On ARM, look at highbank. Because we're not running we're lacking
> >> a monitor mode blob that provides sys calls for flushin
On 05/04/2013 21:24, Anthony Liguori wrote:
Peter Maydell writes:
On 5 April 2013 17:47, Anthony Liguori wrote:
Kevin Wolf writes:
From: KONRAD Frederic
The virtio-blk-x configuration is not in sync with virtio-blk configuration.
So this patch remove the virtio-blk-x configuration field
On (Fri) 05 Apr 2013 [17:59:33], Paolo Bonzini wrote:
> The character backend refactoring introduced an undesirable busy wait.
> The busy wait happens if can_read returns zero and there is data available
> on the character device's file descriptor. Then, the I/O watch will
> fire continuously and,
Guys, perhaps we should move this dialogue to a different thread as we
are abusing the unrelated Bug 1128935.
Jakub
On 04/06/2013 07:01 PM, blueswirl wrote:
> On Sat, Apr 6, 2013 at 9:31 AM, agraf <1128...@bugs.launchpad.net> wrote:
>> Hi Lurie,
>>
>> On 04.04.2013, at 19:34, Iurie wrote:
>>
>>>
On Sat, Apr 6, 2013 at 9:31 AM, agraf <1128...@bugs.launchpad.net> wrote:
> Hi Lurie,
>
> On 04.04.2013, at 19:34, Iurie wrote:
>
>> hello,
>> in the past year gsoc qemu proposed projects there where on eproject that i
>> liked, which were: qemu IA64 emulation :
>> http://wiki.qemu.org/Google_Sum
Change versatile_pci to subclass TYPE_PCI_HOST_BRIDGE and generally
handle PCI in a more QOM-like fashion.
Signed-off-by: Peter Maydell
Acked-by: Paul Brook
---
hw/versatile_pci.c | 41 ++---
1 file changed, 30 insertions(+), 11 deletions(-)
diff --git a/h
Rather than overloading the system I/O space (which doesn't even make
any sense on ARM) for PCI I/O, create an memory region in the PCI
controller and use that to represent the I/O space.
Signed-off-by: Peter Maydell
Acked-by: Paul Brook
---
hw/versatile_pci.c | 17 +
1 file c
Fix the mapping of the PCI regions for the realview board, which were
all incorrect. (This was never noticed because the Linux kernel
doesn't actually include a PCI driver for the realview boards.)
Signed-off-by: Peter Maydell
Acked-by: Paul Brook
---
hw/arm/realview.c | 18 +-
Implement the correct IRQ mapping for the Versatile PCI controller; it
differs between realview and versatile boards, but the previous QEMU
implementation was correct only for the first PCI card on a versatile
board, since we weren't swizzling IRQs based on the slot number.
Since this change would
There is just one line in this source file with a hardcoded tab
indent, so just fix it.
Signed-off-by: Peter Maydell
Acked-by: Paul Brook
---
hw/versatile_pci.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/versatile_pci.c b/hw/versatile_pci.c
index d67ca79..04d0029
Drop the vpb_pci_config_addr() function -- it is unnecessary since
the size of the memory regions means the hwaddr is always within
the 24 bit size. (This function was probably a leftover from when
read/write functions were called with absolute addresses rather
than relative ones.)
Signed-off-by:
This patch series fixes a number of serious bugs in our emulation of
the PCI controller found on VersatilePB and the early Realview boards:
* our interrupt mapping was totally wrong
* we weren't implementing the PCI memory windows
* the I/O window wasn't mapped on VersatilePB
* realview mapped
Comments in the QEMU source code claim that the version of the PCI
controller on the VersatilePB board doesn't support the PCI I/O
region, but this is incorrect; expose that region, map it in the
correct location, and drop the misleading comments.
This change removes the only currently implemented
Update the Versatile PCI controller to use a realize function rather
than SysBusDevice::init. To reflect the fact that the 'realview_pci'
class is taking most of its implementation from 'versatile_pci' (and
to make the QOM casts work) we make 'realview_pci' a subclass of
'versatile_pci'.
Signed-of
On real hardware the host bridge appears as a PCI device in slot 29,
so make QEMU put its host bridge in that slot too.
Signed-off-by: Peter Maydell
Acked-by: Paul Brook
---
hw/versatile_pci.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/hw/versatile_pci.c b/hw/versatile_pci.c
index
hi,
thank you very much for the answer. i will try do some more easy projects
durring this summer related to asm and things like that and i hope in the
following year to do this project.
best regards
On 6 April 2013 10:31, Alexander Graf wrote:
> Hi Lurie,
>
> On 04.04.2013, at 19:34, Iurie wr
The VersatilePB's PCI controller exposes the PCI memory space to the
system via three regions controlled by the mapping control registers.
Implement this so that guests can actually use MMIO-BAR PCI cards.
Signed-off-by: Peter Maydell
Acked-by: Paul Brook
---
hw/arm/realview.c|3 +++
hw
The versatile_pci PCI controller has a set of control registers which
handle the mapping between PCI and system address spaces. Implement
these registers (though for now they have no effect since we don't
implement mapping PCI space into system memory at all).
The most natural order for our sysbus
Thanks, pulled.
On Fri, Apr 5, 2013 at 5:13 PM, Peter Maydell wrote:
> Here's the latest set of arm-devs patches; mostly migration
> related fixes, plus a few random minor bug zaps. Please pull.
>
> thanks
> -- PMM
>
> The following changes since commit d05ef160453e98546a4197496dc8a3cb2defac53:
>
Public bug reported:
executable qemu-1.4.0/i386-linux-user/./qemu-i386 gives a segmentation
fault
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpa
On 6 April 2013 12:38, Alexander Graf wrote:
>
> On 06.04.2013, at 13:27, Peter Maydell wrote:
>
>> On 6 April 2013 10:07, Alexander Graf wrote:
>>> On ARM, look at highbank. Because we're not running we're lacking
>>> a monitor mode blob that provides sys calls for flushing caches.
>>> Thus toda
On 06.04.2013, at 13:27, Peter Maydell wrote:
> On 6 April 2013 10:07, Alexander Graf wrote:
>> On ARM, look at highbank. Because we're not running we're lacking
>> a monitor mode blob that provides sys calls for flushing caches.
>> Thus today the highbank machine doesn't boot anymore with Linux
On 6 April 2013 10:07, Alexander Graf wrote:
> On ARM, look at highbank. Because we're not running we're lacking
> a monitor mode blob that provides sys calls for flushing caches.
> Thus today the highbank machine doesn't boot anymore with Linux.
> If we ran firmware like the real board, that woul
Hi ! I am trying to emulate mips64 on Qemu but the kernel is unable to open
the file /dev/console and gives the warning "unable to open an initial
console" and hangs.i have checked in the initramfs file that /dev/console
node is present in it.Can any one plz tell me that what can be the reason
for
Hi Lurie,
On 04.04.2013, at 19:34, Iurie wrote:
> hello,
> in the past year gsoc qemu proposed projects there where on eproject that i
> liked, which were: qemu IA64 emulation :
> http://wiki.qemu.org/Google_Summer_of_Code_2012#IA64_emulation
>
> this year i have not seen this project to be pr
Am 06.04.2013 um 01:00 schrieb Scott Wood :
> On 04/04/2013 06:59:24 AM, Alexander Graf wrote:
>> On 04.04.2013, at 13:53, Andreas Färber wrote:
>> > For PReP, Fabien has not stated what his use case actually is (in
>> > particular which hardware?), so it's hard for me to comment on what the
>>
On Wed, Apr 3, 2013 at 10:03 AM, Paolo Bonzini wrote:
> From linux-user-test-0.3, running on x86_64:
>
> $ ../sparc32plus-linux-user/qemu-sparc32plus -L ./gnemul/qemu-sparc sparc/ls
This works for me:
/src/qemu/obj-amd64/sparc32plus-linux-user/qemu-sparc32plus -L
./usr/local/gnemul/qemu-sparc sp
Am 06.04.2013 um 01:00 schrieb Scott Wood :
> On 04/04/2013 06:59:24 AM, Alexander Graf wrote:
>> On 04.04.2013, at 13:53, Andreas Färber wrote:
>> > For PReP, Fabien has not stated what his use case actually is (in
>> > particular which hardware?), so it's hard for me to comment on what the
>>
45 matches
Mail list logo
