thank you.
can you tell me what's the difference between memsave and
dump-guest-memory without -p option?
and what's the difference between *kernel coredump *and
dump-guest-memory with -p option?
On 07/19/2012 01:42 PM, Wen Congyang wrote:
At 07/19/2012 12:47 AM, Sheldon Wrote:
I want to dum
At 07/19/2012 03:29 PM, Sheldon Wrote:
> thank you.
> can you tell me what's the difference between memsave and
> dump-guest-memory without -p option?
IIRC, memsave only contains memory. The core generated by
dump-guest-memory contains registers' value, and you can use
crash to deal with it.
> an
From: Wen Congyang
Subject: Re: [Qemu-devel] [help]: how to use HMP command dump-guest-memory
Date: Thu, 19 Jul 2012 15:41:22 +0800
> At 07/19/2012 03:29 PM, Sheldon Wrote:
> kernel coredump? Do you mean kdump?
>
> They are almost the same. The core generated by dump-guest-memory
> contains som
Am 19.07.2012 04:20, schrieb Dong Xu Wang:
> On Thu, Jun 14, 2012 at 7:33 PM, Kevin Wolf wrote:
>> Am 14.06.2012 13:18, schrieb Paolo Bonzini:
>>> Il 14/06/2012 12:59, Kevin Wolf ha scritto:
Am 13.06.2012 16:36, schrieb Dong Xu Wang:
> add-cow will let raw file support snapshot_blkdev ind
yes, try '-mem-path '
On Wed, Jul 18, 2012 at 10:41:43PM +, Haines, Brent R wrote:
On Wed, Jul 18, 2012 at 4:40 PM, Michael S. Tsirkin wrote:
> On Wed, Jul 18, 2012 at 04:07:45PM +0100, Stefan Hajnoczi wrote:
>> Optimize for the MSI-X enabled and vector unmasked case where it is
>> possible to issue the KVM ioctl() directly instead of using irqfd.
>
> Why? Is an ioctl faster?
I
On Wed, Jul 18, 2012 at 7:29 PM, Michael S. Tsirkin wrote:
> On Wed, Jul 18, 2012 at 04:07:33PM +0100, Stefan Hajnoczi wrote:
>> Support >4 GB physical memory accesses.
>>
>> Signed-off-by: Stefan Hajnoczi
>
> Need some sane APIs, this is just too scary.
Yes, this prototype has (at least) two la
On Thu, Jul 19, 2012 at 10:14 AM, Stefan Hajnoczi wrote:
> On Wed, Jul 18, 2012 at 7:29 PM, Michael S. Tsirkin wrote:
>> On Wed, Jul 18, 2012 at 04:07:33PM +0100, Stefan Hajnoczi wrote:
>>> Support >4 GB physical memory accesses.
>>>
>>> Signed-off-by: Stefan Hajnoczi
>>
>> Need some sane APIs,
Yes, I have used same drive_get(IF_PFLASH, 0, 0) with two flashes.
As these flashes are two different banks with individual bases address, I
used the same.
Was there any block allocation problem with this..will you please elaborate.
I couldn't understand about drive_get_next(), I think function c
On Thu, Jul 19, 2012 at 10:11:49AM +0100, Stefan Hajnoczi wrote:
> On Wed, Jul 18, 2012 at 4:40 PM, Michael S. Tsirkin wrote:
> > On Wed, Jul 18, 2012 at 04:07:45PM +0100, Stefan Hajnoczi wrote:
> >> Optimize for the MSI-X enabled and vector unmasked case where it is
> >> possible to issue the KVM
On 07/19/2012 03:41 PM, Wen Congyang wrote:
At 07/19/2012 03:29 PM, Sheldon Wrote:
thank you.
can you tell me what's the difference between memsave and
dump-guest-memory without -p option?
IIRC, memsave only contains memory. The core generated by
dump-guest-memory contains registers' value, and
On Thu, Jul 19, 2012 at 10:32:40AM +1000, Alexey Kardashevskiy wrote:
> On 19/07/12 01:23, Michael S. Tsirkin wrote:
> > On Wed, Jul 18, 2012 at 11:17:12PM +1000, Alexey Kardashevskiy wrote:
> >> On 18/07/12 22:43, Michael S. Tsirkin wrote:
> >>> On Thu, Jun 21, 2012 at 09:39:10PM +1000, Alexey Kar
On Thu, Jul 19, 2012 at 10:35:07AM +1000, Alexey Kardashevskiy wrote:
> Added (msi|msix)_set_message() function for whoever might
> want to use them.
>
> Currently msi_notify()/msix_notify() write to these vectors to
> signal the guest about an interrupt so the correct values have to
> written the
On 07/19/2012 12:16 PM, Stefan Hajnoczi wrote:
> On Thu, Jul 19, 2012 at 10:14 AM, Stefan Hajnoczi wrote:
>> On Wed, Jul 18, 2012 at 7:29 PM, Michael S. Tsirkin wrote:
>>> On Wed, Jul 18, 2012 at 04:07:33PM +0100, Stefan Hajnoczi wrote:
Support >4 GB physical memory accesses.
Signe
On Wed, Jul 18, 2012 at 4:49 PM, Michael S. Tsirkin wrote:
> On Wed, Jul 18, 2012 at 04:07:27PM +0100, Stefan Hajnoczi wrote:
>> This series implements a dedicated thread for virtio-blk processing using
>> Linux
>> AIO for raw image files only. It is based on qemu-kvm.git a0bc8c3 and
>> somewha
On Thu, Jul 19, 2012 at 3:20 AM, Dong Xu Wang
wrote:
> On Thu, Jun 14, 2012 at 7:33 PM, Kevin Wolf wrote:
>> Am 14.06.2012 13:18, schrieb Paolo Bonzini:
>>> Il 14/06/2012 12:59, Kevin Wolf ha scritto:
Am 13.06.2012 16:36, schrieb Dong Xu Wang:
> add-cow will let raw file support snapshot
On Tue, Jul 17, 2012 at 06:56:30PM -0300, Eduardo Habkost wrote:
> This patch is an attempt to fix the non-continguous-APIC-ID problem without
> the
> FW_CFG_LAPIC_INFO approach I have sent proposed last week.
>
> Basically, this changes Seabios to probe for APIC IDs directly from the
> CPUs on b
From: Harsh Prateek Bora
Support new tracelog format for multiple arguments and strings.
Signed-off-by: Harsh Prateek Bora
Signed-off-by: Stefan Hajnoczi
---
scripts/simpletrace.py | 116 +++-
1 file changed, 75 insertions(+), 41 deletions(-)
diff
Simpletrace v2 has landed:
* Strings are now logged instead of their pointers
* Variable-length arguments allow for >6 trace event arguments
Thanks to Harsh Prateek Bora for this improvement!
The following changes since commit dfe1ce5d80cba603bafaac91b239d683abe19cf7:
Merge remote-tracking b
From: Harsh Prateek Bora
Going forward with simpletrace v2 variable size trace records, we cannot
have a generic function to print trace event info and therefore this
interface becomes invalid.
As per Stefan Hajnoczi:
"This command is only available from the human monitor. It's not very
useful
From: Alexey Kardashevskiy
It is convenient for debug to be able to switch on/off some events easily.
The only possibility now is to remove event name from the file completely
and type it again when we want it back.
The patch adds '#' symbol handling as a comment specifier.
Signed-off-by: Alexe
From: Harsh Prateek Bora
Existing simpletrace backend allows to trace at max 6 args and does not
support strings. This newer tracelog format gets rid of fixed size records
and therefore allows to trace variable number of args including strings.
Sample trace with strings:
v9fs_version 0.000 tag=0
Going forward with simpletrace v2 variable size trace records, we cannot
have a generic function to print trace event info and therefore this
interface becomes invalid.
As per Stefan Hajnoczi:
"This command is only available from the human monitor. It's not very
useful because it historically ha
Hi; I'm a bit confused about handling of passing interrupts
to KVM from QEMU.
Looking at a few of the current platforms:
x86, no in-kernel irqchip:
* we seem to use the usual non-KVM cpu_interrupt() and
cpu_reset_interrupt() functions, which in a KVM enabled QEMU
set flags in env->interrup
Ping?
On 2012년 07월 17일 11:06, YeongKyoon Lee wrote:
> The reason why softmmu condition in configure is that softmmu is thought to
> be a logical prerequisite of ldst optimization.
> Current patch causes compilation error if removed the condition above.
> To avoid compilation error, it needs more
Support new tracelog format for multiple arguments and strings.
Signed-off-by: Harsh Prateek Bora
---
scripts/simpletrace.py | 116 +++-
1 file changed, 75 insertions(+), 41 deletions(-)
diff --git a/scripts/simpletrace.py b/scripts/simpletrace.py
in
Existing simpletrace backend allows to trace at max 6 args and does not
support strings. This newer tracelog format gets rid of fixed size records
and therefore allows to trace variable number of args including strings.
Sample trace:
v9fs_version 0.000 tag=0x id=0x64 msize=0x2000 version=9P200
Existing simpletrace backend allows to trace at max 6 args and does not
support strings. This newer tracelog format gets rid of fixed size records
and therefore allows to trace variable number of args including strings.
Sample trace with strings:
v9fs_version 0.000 tag=0x id=0x64 msize=0x2000
Il 18/07/2012 17:35, Daniel P. Berrange ha scritto:
> Oh, and will this library depend on glib
Yes, in all likelihood.
, and will it have the
> abort-on-oom behaviour QEMU has ? From a libvirt POV, we won't
> use any library that aborts-on-oom.
Out of curiosity, how do you test OOM?
Paolo
On 17/07/12 19:36, Stefano Stabellini wrote:
On Tue, 17 Jul 2012, Avi Kivity wrote:
How about pushing the call into cpu_physical_memory_set_dirty_flags()?
Would that reduce the number of call sites?
Pushing the calls to cpu_physical_memory_set_dirty_flags and
cpu_physical_memory_set_dirty_rang
On 07/19/2012 02:14 PM, Peter Maydell wrote:
>
> Basically I'm not sure why there's all this variety here,
> or why x86 does things differently for in-kernel irqchip
> versus not -- I would have expected that the only difference
> for an in-kernel irqchip is that there are more interrupt
> lines.
On 07/19/2012 02:41 PM, Anthony PERARD wrote:
> On 17/07/12 19:36, Stefano Stabellini wrote:
>> On Tue, 17 Jul 2012, Avi Kivity wrote:
>>> How about pushing the call into cpu_physical_memory_set_dirty_flags()?
>>> Would that reduce the number of call sites?
>>
>> Pushing the calls to cpu_physical_m
On Thu, Jul 19, 2012 at 12:07 PM, Harsh Prateek Bora
wrote:
> Existing simpletrace backend allows to trace at max 6 args and does not
> support strings. This newer tracelog format gets rid of fixed size records
> and therefore allows to trace variable number of args including strings.
>
> Sample t
On 07/19/2012 04:22 PM, Stefan Hajnoczi wrote:
Simpletrace v2 has landed:
* Strings are now logged instead of their pointers
* Variable-length arguments allow for >6 trace event arguments
Thanks to Harsh Prateek Bora for this improvement!
Thanks very much to Stefan Hajnoczi for his effecti
On 07/19/2012 05:22 PM, Stefan Hajnoczi wrote:
On Thu, Jul 19, 2012 at 12:07 PM, Harsh Prateek Bora
wrote:
Existing simpletrace backend allows to trace at max 6 args and does not
support strings. This newer tracelog format gets rid of fixed size records
and therefore allows to trace variable nu
On 19 July 2012 12:43, Avi Kivity wrote:
> On 07/19/2012 02:14 PM, Peter Maydell wrote:
>>
>> Basically I'm not sure why there's all this variety here,
>> or why x86 does things differently for in-kernel irqchip
>> versus not -- I would have expected that the only difference
>> for an in-kernel ir
Il 17/07/2012 20:06, Stefano Stabellini ha scritto:
> On Tue, 17 Jul 2012, Anthony PERARD wrote:
>> This patch add some calls to xen_modified_memory to notify Xen about
>> dirtybits
>> during migration.
>>
>> Signed-off-by: Anthony PERARD
>> ---
>> exec.c |4
>> memory.c |2 ++
>>
On Thu, 19 Jul 2012 10:17:10 +0200
Kevin Wolf wrote:
> Am 19.07.2012 04:20, schrieb Dong Xu Wang:
> > On Thu, Jun 14, 2012 at 7:33 PM, Kevin Wolf wrote:
> >> Am 14.06.2012 13:18, schrieb Paolo Bonzini:
> >>> Il 14/06/2012 12:59, Kevin Wolf ha scritto:
> Am 13.06.2012 16:36, schrieb Dong Xu
On Mon, Jul 02, 2012 at 02:38:46PM +0200, Jan Kiszka wrote:
> Add a PCI IRQ path discovery function that walks from a given device to
> the host bridge, returning the mode (enabled/inverted/disabled) and the
> IRQ number that is reported to the attached interrupt controller. For
> this purpose, ano
tcp_chr_write() did not deal with writing to an unconnected
connection and return the original length of the data, it's
not right and would cause false writing. So (re-)connect it
and return 0 for this situation.
Signed-off-by: Lei Li
---
qemu-char.c |7 +--
1 files changed, 5 insertions
On 07/19/2012 02:00 PM, Peter Maydell wrote:
On 19 July 2012 12:43, Avi Kivity wrote:
On 07/19/2012 02:14 PM, Peter Maydell wrote:
Basically I'm not sure why there's all this variety here,
or why x86 does things differently for in-kernel irqchip
versus not -- I would have expected that the onl
On Mon, Jul 02, 2012 at 02:38:47PM +0200, Jan Kiszka wrote:
> This per-device notifier shall be triggered by any interrupt router
> along the path of a device's legacy interrupt signal on routing changes.
> For simplicity reasons and as this is a slow path anyway, no further
> details on the routin
On 19 July 2012 15:13, Alexander Graf wrote:
> On 07/19/2012 02:00 PM, Peter Maydell wrote:
>> On 19 July 2012 12:43, Avi Kivity wrote:
>>> Let's make them even more similar, by removing !in_kernel_irqchip.
>>
>> Mmm, I do rather want to just mandate use of the VGIC...
>> (somebody will probably
hi,
while playing with various qemu versions i noticed that
qemu-devel now in FreeBSD ports (1.1.0) is slow as hell when
booting FreeBSD (take for instance the netmap image at
http://info.iet.unipi.it/~luigi/netmap/20120608-netmap-picobsd-head-amd64.bin
while 0.11.x and 1.1.1 and 1.0.1 seem to wo
One comment below.
On 19/07/12 19:27, Michael S. Tsirkin wrote:
> On Thu, Jul 19, 2012 at 10:32:40AM +1000, Alexey Kardashevskiy wrote:
>> On 19/07/12 01:23, Michael S. Tsirkin wrote:
>>> On Wed, Jul 18, 2012 at 11:17:12PM +1000, Alexey Kardashevskiy wrote:
On 18/07/12 22:43, Michael S. Tsir
On 19/07/12 12:50, Avi Kivity wrote:
On 07/19/2012 02:41 PM, Anthony PERARD wrote:
On 17/07/12 19:36, Stefano Stabellini wrote:
On Tue, 17 Jul 2012, Avi Kivity wrote:
How about pushing the call into cpu_physical_memory_set_dirty_flags()?
Would that reduce the number of call sites?
Pushing th
On Thu, Jul 19, 2012 at 12:58:46PM +0300, Gleb Natapov wrote:
> On Tue, Jul 17, 2012 at 06:56:30PM -0300, Eduardo Habkost wrote:
> > This patch is an attempt to fix the non-continguous-APIC-ID problem without
> > the
> > FW_CFG_LAPIC_INFO approach I have sent proposed last week.
> >
> > Basically
I've been using this to get correct indenting with vim
in qemu for a while, but it's a bit easier if we
put the settings in the central place.
Note that
1. you still need to enable 'exrc' and 'secure'
options in your vimrc for these settings to take effect.
2. you can create a .vimrc file if 'ex
On 07/19/2012 04:16 PM, Peter Maydell wrote:
On 19 July 2012 15:13, Alexander Graf wrote:
On 07/19/2012 02:00 PM, Peter Maydell wrote:
On 19 July 2012 12:43, Avi Kivity wrote:
Let's make them even more similar, by removing !in_kernel_irqchip.
Mmm, I do rather want to just mandate use of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Thierry,
Am 17.07.2012 17:46, schrieb Thierry Reding:
> I've been toying around with adding NVIDIA Tegra support to QEMU.
> While adding SMP support I came across a problem: on Tegra, the
> secondary CPU is kept in reset by the clock-and-reset cont
On Mon, Jul 16, 2012 at 2:45 PM, Peter Maydell wrote:
> On 16 July 2012 11:15, Jing Huang wrote:
>> This patch excludes SO_TIMESTAMP cmsg_type from unsuppoted ancillary data.
>
> "unsupported".
>
>>
>> Signed-off-by: Jing Huang
>> ---
>> linux-user/syscall.c |4 +++-
>> 1 files changed, 3 i
On 19 July 2012 15:33, Jing Huang wrote:
> On Mon, Jul 16, 2012 at 2:45 PM, Peter Maydell
> wrote:
>> On 16 July 2012 11:15, Jing Huang wrote:
>>> This patch excludes SO_TIMESTAMP cmsg_type from unsuppoted ancillary data.
>>
>> "unsupported".
>>
>>>
>>> Signed-off-by: Jing Huang
>>> ---
>>> l
On Fri, Jul 20, 2012 at 12:24:05AM +1000, Alexey Kardashevskiy wrote:
> One comment below.
>
>
> On 19/07/12 19:27, Michael S. Tsirkin wrote:
> > On Thu, Jul 19, 2012 at 10:32:40AM +1000, Alexey Kardashevskiy wrote:
> >> On 19/07/12 01:23, Michael S. Tsirkin wrote:
> >>> On Wed, Jul 18, 2012 at 1
I've been using this to get correct indenting with vim
in qemu for a while, but it's a bit easier if we
put the settings in the central place.
Note that
1. you still need to enable 'exrc' and 'secure'
options in your vimrc for these settings to take effect.
2. you can create a .vimrc file if 'ex
On 20/07/12 00:43, Michael S. Tsirkin wrote:
> On Fri, Jul 20, 2012 at 12:24:05AM +1000, Alexey Kardashevskiy wrote:
>> One comment below.
>>
>>
>> On 19/07/12 19:27, Michael S. Tsirkin wrote:
>>> On Thu, Jul 19, 2012 at 10:32:40AM +1000, Alexey Kardashevskiy
>>> wrote:
On 19/07/12 01:23, Mi
On Fri, Jul 20, 2012 at 12:50:26AM +1000, Alexey Kardashevskiy wrote:
> On 20/07/12 00:43, Michael S. Tsirkin wrote:
> > On Fri, Jul 20, 2012 at 12:24:05AM +1000, Alexey Kardashevskiy wrote:
> >> One comment below.
> >>
> >>
> >> On 19/07/12 19:27, Michael S. Tsirkin wrote:
> >>> On Thu, Jul 19,
On 19 July 2012 15:29, Michael S. Tsirkin wrote:
> I've been using this to get correct indenting with vim
> in qemu for a while, but it's a bit easier if we
> put the settings in the central place.
> Note that
> 1. you still need to enable 'exrc' and 'secure'
>options in your vimrc for these s
The following changes since commit 80aa796bf38b7ef21daa42673b4711510c450d8a:
pci_bridge_dev: fix error path in pci_bridge_dev_initfn() (2012-06-11
22:55:13 +0300)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_anthony
for you to fetch ch
Thanks for the response. I should have said in the original post that the
-mem-path and -mem-prealloc flags do not do what I need them to do. Using the
-mem-path flag passes the hugepage to the guest but does not make the hugepage
still available to the host. I want to be able to allocate hug
On Thu, Jul 19, 2012 at 04:11:21PM +0100, Peter Maydell wrote:
> On 19 July 2012 15:29, Michael S. Tsirkin wrote:
> > I've been using this to get correct indenting with vim
> > in qemu for a while, but it's a bit easier if we
> > put the settings in the central place.
> > Note that
> > 1. you stil
I'm interested in using QEMU to test gcc for a processor.
This is a hard-metal target -- there is no operating system.
Can anyone make suggestions on how to do this?
--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
On Thu, 19 Jul 2012, Paolo Bonzini wrote:
> Il 17/07/2012 20:06, Stefano Stabellini ha scritto:
> > On Tue, 17 Jul 2012, Anthony PERARD wrote:
> >> This patch add some calls to xen_modified_memory to notify Xen about
> >> dirtybits
> >> during migration.
> >>
> >> Signed-off-by: Anthony PERARD
>
On Sun, Jun 24, 2012 at 4:11 PM, Zhi Yong Wu wrote:
> pull?
I have been basing work off this series. I'm sending a rebased and
retested version which applies to current qemu.git/master.
Stefan
Il 19/07/2012 17:40, Stefan Hajnoczi ha scritto:
> On Sun, Jun 24, 2012 at 4:11 PM, Zhi Yong Wu wrote:
>> > pull?
> I have been basing work off this series. I'm sending a rebased and
> retested version which applies to current qemu.git/master.
We need to coordinate between this series and Laszlo
On Thu, Jul 19, 2012 at 4:37 PM, Stefano Stabellini
wrote:
>
> Anthony, can you write a patch to change the behavior in
> qemu-xen-traditional too?
Yes.
--
Anthony PERARD
On Thu, Jul 19, 2012 at 11:41 PM, Paolo Bonzini wrote:
> Il 19/07/2012 17:40, Stefan Hajnoczi ha scritto:
>> On Sun, Jun 24, 2012 at 4:11 PM, Zhi Yong Wu wrote:
>>> > pull?
>> I have been basing work off this series. I'm sending a rebased and
>> retested version which applies to current qemu.git
On Thu, Jul 19, 2012 at 4:41 PM, Paolo Bonzini wrote:
> Il 19/07/2012 17:40, Stefan Hajnoczi ha scritto:
>> On Sun, Jun 24, 2012 at 4:11 PM, Zhi Yong Wu wrote:
>>> > pull?
>> I have been basing work off this series. I'm sending a rebased and
>> retested version which applies to current qemu.git/
Il 19/07/2012 17:48, Zhi Yong Wu ha scritto:
>>> >> I have been basing work off this series. I'm sending a rebased and
>>> >> retested version which applies to current qemu.git/master.
>> >
>> > We need to coordinate between this series and Laszlo's QemuOpts conversion.
> How to coordinate? Look a
Commit 946fb27c1 moved all the uses of all_cpu_threads_idle()
into cpus.c. This means we can mark the function 'static'
(again), if we shuffle it a bit earlier in the source file.
Signed-off-by: Peter Maydell
---
cpus.c| 52 ++--
qemu-com
qapi/opts-visitor.h | 31
qapi/opts-visitor.c | 427 +++
qapi/Makefile.objs |2 +-
3 files changed, 459 insertions(+), 1 deletions(-)
create mode 100644 qapi/opts-visitor.h
create mode 100644 qapi/opts-visitor.c
>From the above log of
Signed-off-by: Jan Kiszka
---
configure |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/configure b/configure
index 106209a..42adc8d 100755
--- a/configure
+++ b/configure
@@ -90,8 +90,8 @@ static="no"
sparc_cpu=""
cross_prefix=""
audio_drv_list=""
-audio_card_list=
On Thu, Jul 19, 2012 at 5:29 PM, Michael Eager wrote:
> I'm interested in using QEMU to test gcc for a processor.
> This is a hard-metal target -- there is no operating system.
>
> Can anyone make suggestions on how to do this?
You could look at how QEMU implements semihosting for ARM.
And also h
Il 19/07/2012 17:57, Zhi Yong Wu ha scritto:
> qapi/opts-visitor.h | 31
> qapi/opts-visitor.c | 427
> +++
> qapi/Makefile.objs |2 +-
> 3 files changed, 459 insertions(+), 1 deletions(-)
> create mode 100644 qapi/opts-visitor.h
> cr
On 07/19/2012 08:59 AM, Laurent Desnogues wrote:
On Thu, Jul 19, 2012 at 5:29 PM, Michael Eager wrote:
I'm interested in using QEMU to test gcc for a processor.
This is a hard-metal target -- there is no operating system.
Can anyone make suggestions on how to do this?
You could look at how Q
Hi,
This patch series adds more scsi support to seabios. I've hacked up a
UAS (usb attached scsi) driver, so you can boot from upcoming[1] uas
devices. And while being at it I also added lsi53c895a support,
allowing qemu boot from lsi without depending on the extboot hack.
enjoy,
Gerd
PS:
This patch adds support for the lsi53c895a scsi host adapter,
allowing seabios to boot from scsi disks and cdroms connected
to the lsi scsi hba emulated by qemu.
This driver was written by looking at the expectations of qemu's
lsi emulation. I have no idea idea how close this is to work on
real h
This patch adds support for booting from UAS (usb
attached scsi) devices.
For now only usb 2.0 support is there. On usb 3.0 the
UAS protocol uses streams, so changes will be required
to make usb 3.0 devices fly once we have a xhci host
controller driver.
So far the driver has been tested on qemu
net.h | 16 +--
net/dump.h |5 +-
net/slirp.h|4 +-
net/socket.h |5 +-
net/tap.h | 10 +-
net/vde.h |5 +-
net.c | 494 +++
On Thu, 19 Jul 2012, Jan Kiszka wrote:
> Signed-off-by: Jan Kiszka
> ---
> configure |4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
Applied, thanks.
--
mailto:av1...@comtv.ru
Hello Stefan,
On 07/19/12 17:48, Stefan Hajnoczi wrote:
> On Thu, Jul 19, 2012 at 4:41 PM, Paolo Bonzini wrote:
>> Il 19/07/2012 17:40, Stefan Hajnoczi ha scritto:
>>> On Sun, Jun 24, 2012 at 4:11 PM, Zhi Yong Wu wrote:
> pull?
>>> I have been basing work off this series. I'm sending a reba
On 07/19/2012 01:16 PM, jagan wrote:
Yes, I have used same drive_get(IF_PFLASH, 0, 0) with two flashes.
As these flashes are two different banks with individual bases address,
I used the same.
Was there any block allocation problem with this..will you please elaborate.
I couldn't understand abo
From: Corey Minyard
When an open event is reported, it is done through a bh. But close
events are reported immediately. So if an open event is in the bh
and a close occurs, an extraneous open happens, which can confuse a
user.
To fix this, this patch sets the "opened" flag immediately instead
From: Corey Minyard
When setting an object, if you don't release the previous object
that was there, it may become unusable. This change allows a
chardev to be removed from one object's properties and added to
another's.
Signed-off-by: Corey Minyard
Acked-by: Paolo Bonzini
---
qom/object.c |
Ok, everything passes through checkpatch without an error now. I have
added some tests to verify basic operation of the device, and I've
hacked in some documentation, though I'm not sure if it's in the proper
location, as I never got a response to my questions about it.
I would have liked to add
Paolo Bonzini writes:
> This takes the eventfd emulation code from the main loop and adds it
> to EventNotifier. When the EventNotifier is used for the main loop too,
> we need this compatibility code.
>
> Without CONFIG_EVENTFD, event_notifier_get_fd is only usable for the
> "read" side of the
From: Corey Minyard
Test the KCS interface with a local BMC and a BT interface with an
external BMC.
Signed-off-by: Corey Minyard
---
tests/Makefile|4 +
tests/ipmi-test-bt.c | 440 +
tests/ipmi-test-kcs.c | 295 +++
Paolo Bonzini writes:
Reviewed-by: Anthony Liguori
Regards,
Anthony Liguori
> Signed-off-by: Paolo Bonzini
> ---
> Makefile.objs |4 +--
> main-loop.c | 106
> -
> oslib-posix.c | 31 -
> qemu-common.h |1
From: Corey Minyard
This provides the simulation of the KCS hardware interface.
Signed-off-by: Corey Minyard
---
default-configs/i386-softmmu.mak |1 +
default-configs/x86_64-softmmu.mak |1 +
hw/Makefile.objs |1 +
hw/ipmi_kcs.c | 337
Paolo Bonzini writes:
> Since linux-aio already uses an eventfd, converting it to use the
> EventNotifier-based API simplifies the code even though it is not
> meant to be portable.
>
Reviewed-by: Anthony Liguori
Regards,
Anthony Liguori
> Signed-off-by: Paolo Bonzini
> ---
> linux-aio.c |
From: Corey Minyard
Some devices may need to do some firmware-type initialization before
the firmware itself is initialized. For instance, any device that
adds SMBIOS table entries (like IPMI) will need to do that before
the BIOS is initialized.
So add a list of devices that get initialized bef
From: Corey Minyard
This provides a minimal local BMC, basically enough to comply with the
spec and provide a complete watchdog timer (including a sensor, SDR,
and event).
Signed-off-by: Corey Minyard
---
default-configs/i386-softmmu.mak |1 +
default-configs/x86_64-softmmu.mak |1 +
From: Corey Minyard
This will result in a double free on close, because it's freed
in qemu_chr_delete() right after calling the close function.
Signed-off-by: Corey Minyard
---
qemu-char.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/qemu-char.c b/qemu-char.c
index
On Thu, Jul 19, 2012 at 11:28:54AM -0300, Eduardo Habkost wrote:
> On Thu, Jul 19, 2012 at 12:58:46PM +0300, Gleb Natapov wrote:
> > On Tue, Jul 17, 2012 at 06:56:30PM -0300, Eduardo Habkost wrote:
> > > This patch is an attempt to fix the non-continguous-APIC-ID problem
> > > without the
> > > FW
From: Corey Minyard
Add the basic IPMI types and infrastructure to QEMU. Low-level
interfaces and simulation interfaces will register with this; it's
kind of the go-between to tie them together.
Signed-off-by: Corey Minyard
---
default-configs/i386-softmmu.mak |1 +
default-configs/x86_
From: Corey Minyard
This provides the simulation of the BT hardware interface for
IPMI.
Signed-off-by: Corey Minyard
---
default-configs/i386-softmmu.mak |1 +
default-configs/x86_64-softmmu.mak |1 +
hw/Makefile.objs |1 +
hw/ipmi_bt.c |
From: Corey Minyard
The chardev backends that used qemu_chr_open_fd did not get their
file descriptors closed at end of file or when the chardev was closed.
This could result in a file descriptor leak.
Signed-off-by: Corey Minyard
---
qemu-char.c | 31 +--
1 files
From: Corey Minyard
There was no way to directly add a table entry to the SMBIOS table,
even though the BIOS supports this. So add a function to do this.
This is in preparation for the IPMI handler adding it's SMBIOS table
entry.
Signed-off-by: Corey Minyard
---
hw/smbios.c | 27 +++
From: Corey Minyard
This allocates the CharDriverState structure in a more logical place.
It reduces code size and it allows a coming option to automatically
attempt to reconnect a chardev if the connection fails.
Signed-off-by: Corey Minyard
---
console.c |6 +---
console.h
From: Corey Minyard
Allow a socket that connects to reconnect on a periodic basis if it
fails to connect at startup or if the connection drops while in use.
Signed-off-by: Corey Minyard
---
qemu-char.c | 62 ++
qemu-char.h |4 ++
From: Corey Minyard
The timers may be used in initialization, so move them earlier so they
are ready. A reconnect options will be added to qemu-char, and it uses
a timer, but the timer alarm wasn't initialized yet.
Signed-off-by: Corey Minyard
---
vl.c | 10 +-
1 files changed, 5 in
1 - 100 of 137 matches
Mail list logo
