On Wed, Sep 01, 2010 at 10:10:30PM +0200, Stefan Weil wrote:
+static inline void pci_memory_read(PCIDevice *dev,
+ pcibus_t addr,
+ uint8_t *buf,
+ pcibus_t len)
+{
+ pci_memory_rw(dev, addr, buf, len, 0);
+}
+
+static inline void pci_memory_write(PCIDevice *dev,
+ pcibus_t addr,
+
On Thu, Sep 2, 2010 at 5:49 AM, chandra shekar
chandrashekar...@gmail.com wrote:
hello every one can any one tell which part of code or file in qemu deals
with snapshots
any help or suggestions,thanks
There are two features called snapshot in QEMU:
1. The -snapshot mode creates a temporary
On Thu, Sep 02, 2010 at 08:28:26AM +0300, Michael S. Tsirkin wrote:
On Sat, Aug 28, 2010 at 05:54:53PM +0300, Eduard - Gabriel Munteanu wrote:
PCI devices should access memory through pci_memory_*() instead of
cpu_physical_memory_*(). This also provides support for translation and
access
On Thu, Sep 02, 2010 at 09:00:46AM +0300, Michael S. Tsirkin wrote:
On Wed, Sep 01, 2010 at 10:10:30PM +0200, Stefan Weil wrote:
+static inline void pci_memory_read(PCIDevice *dev,
+ pcibus_t addr,
+ uint8_t *buf,
+ pcibus_t len)
+{
+ pci_memory_rw(dev, addr, buf, len, 0);
+}
+
implement secondary bus reset.
Signed-off-by: Isaku Yamahata yamah...@valinux.co.jp
---
hw/pci.c | 13 -
1 files changed, 12 insertions(+), 1 deletions(-)
diff --git a/hw/pci.c b/hw/pci.c
index e23ac1b..183f595 100644
--- a/hw/pci.c
+++ b/hw/pci.c
@@ -1626,6 +1626,9 @@ static void
make pci reset use qdev reset frame work.
Signed-off-by: Isaku Yamahata yamah...@valinux.co.jp
---
hw/pci.c | 38 ++
hw/pci.h |2 ++
2 files changed, 36 insertions(+), 4 deletions(-)
diff --git a/hw/pci.c b/hw/pci.c
index 655fead..4c99390 100644
---
teach pci devices that have reset callback how to reset common registers.
Signed-off-by: Isaku Yamahata yamah...@valinux.co.jp
---
hw/e1000.c |1 +
hw/lsi53c895a.c |2 ++
hw/pci.c|6 --
hw/pcnet.c |1 +
hw/rtl8139.c|2 ++
hw/virtio-pci.c |1 +
6
Make qbus_walk_children() call busfn for root bus.
and it fixes qbus_realize_all().
The current qbus_walk_children() doesn't call busfn for root bus.
It cause qbus_relialize_all() to fail to call realize the system bus.
This patch also refactor qbus_walk_children() a bit.
Another only user of
On Thu, Sep 02, 2010 at 08:19:11AM +0300, Michael S. Tsirkin wrote:
On Sat, Aug 28, 2010 at 05:54:55PM +0300, Eduard - Gabriel Munteanu wrote:
Emulated PCI IDE controllers now use the memory access interface. This
also allows an emulated IOMMU to translate and check accesses.
Map
** Bug watch added: Red Hat Bugzilla #623188
https://bugzilla.redhat.com/show_bug.cgi?id=623188
** Also affects: virt-manager via
https://bugzilla.redhat.com/show_bug.cgi?id=623188
Importance: Unknown
Status: Unknown
--
LVM backed drives should default to cache='none'
Am 02.09.2010 11:38, schrieb Stefan Hajnoczi:
There is no indication whether or not the sector is allocated when
nb_sectors=1:
sector allocated at offset 64 KiB
This message is produced whether or not the sector is allocated.
Simply use the same message as the plural case, I don't
On Thu, Sep 02, 2010 at 12:12:00PM +0300, Eduard - Gabriel Munteanu wrote:
On Thu, Sep 02, 2010 at 08:19:11AM +0300, Michael S. Tsirkin wrote:
On Sat, Aug 28, 2010 at 05:54:55PM +0300, Eduard - Gabriel Munteanu wrote:
Emulated PCI IDE controllers now use the memory access interface. This
On Thu, Sep 02, 2010 at 12:58:13PM +0300, Michael S. Tsirkin wrote:
On Thu, Sep 02, 2010 at 12:12:00PM +0300, Eduard - Gabriel Munteanu wrote:
On Thu, Sep 02, 2010 at 08:19:11AM +0300, Michael S. Tsirkin wrote:
On Sat, Aug 28, 2010 at 05:54:55PM +0300, Eduard - Gabriel Munteanu wrote:
I
Based on a patch from Mark McLoughlin, this patch introduces a new
bottom half packet transmitter that avoids the latency imposed by
the tx_timer approach. Rather than scheduling a timer when a TX
packet comes in, schedule a bottom half to be run from the iothread.
The bottom half handler first
On Thu, Sep 02, 2010 at 06:01:35PM +0300, Eduard - Gabriel Munteanu wrote:
On Thu, Sep 02, 2010 at 12:58:13PM +0300, Michael S. Tsirkin wrote:
On Thu, Sep 02, 2010 at 12:12:00PM +0300, Eduard - Gabriel Munteanu wrote:
On Thu, Sep 02, 2010 at 08:19:11AM +0300, Michael S. Tsirkin wrote:
On
On Thu, Sep 02, 2010 at 09:00:42AM -0600, Alex Williamson wrote:
Incorporated feedback. txburst= and txtimer= are now x- prefixed
developer options. I added a tx= option, because I do want there to
be a supported way to switch between TX strategies. This also drops
the magic value of
De-couple this from the timer since we might want to use
different backends to send the packet.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
hw/virtio-net.c | 18 +-
1 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/hw/virtio-net.c
Am 02.09.2010 10:51, schrieb Eduard - Gabriel Munteanu:
On Wed, Sep 01, 2010 at 10:10:30PM +0200, Stefan Weil wrote:
Please see my comments at the end of this mail.
Am 30.08.2010 00:08, schrieb Eduard - Gabriel Munteanu:
PCI devices should access memory through pci_memory_*()
On 09/02/2010 06:39 PM, Michael S. Tsirkin wrote:
On Thu, Sep 02, 2010 at 06:24:25PM +0300, Avi Kivity wrote:
That's not a practical long term solution. Eventually everything
gets turned on.
That's why I wanted a simple !iommu check and fallback.
This way unless it's really used there's no
When making copy of arguments we were doing partial copy
Signed-off-by: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
---
vl.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/vl.c b/vl.c
index 9f7358e..df11ab3 100644
--- a/vl.c
+++ b/vl.c
@@ -2332,7 +2332,7 @@ int
On Thu, Sep 02, 2010 at 06:05:39PM +0200, Stefan Weil wrote:
Am 02.09.2010 10:51, schrieb Eduard - Gabriel Munteanu:
[snip]
The functions pci_memory_read and pci_memory_write not only read
or write byte data but many different data types which leads to
a lot of type casts in your other
Incorporated feedback. txburst= and txtimer= are now x- prefixed
developer options. I added a tx= option, because I do want there to
be a supported way to switch between TX strategies. This also drops
the magic value of txtimer= 1 or 0 (setting default timeout or switching
modes). I also
On Thu, Sep 02, 2010 at 05:50:09PM +0200, Kevin Wolf wrote:
On Linux, we have code to detect CD-ROMs using an ioctl. We shouldn't lose
anything but false positives by removing the check for a /dev/cd* path.
Agreed.
Reviewed-by: Christoph Hellwig h...@lst.de
I've tried everything you mentioned and I still get the same problem. The only
thing that seems to avoid that issue is if I reduce the aperture size from
0x20ull to 0x200ull.
Here is the relevant section of code:
static const unsigned long long BAR_Regions[6][2] =
{
// len ,
Does any gdb version work with current qemu-system-sparc64 ?
I tried 7.1 and 6.8 with --target=sparc64-linux and --target=sparc64
And result seems to be pretty much the same:
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This patch series is a consolidated view of various VirtFS patches on the
Mailing List. None of these patches are new in this series.
For sometime all these patches were on the mainling list individually.
Changes from V4:
- Added two patches:
o
From: M. Mohan Kumar mo...@in.ibm.com
Make 9P server recognize 9P2000.L protocol version
Signed-off-by: M. Mohan Kumar mo...@in.ibm.com
Signed-off-by: Venkateswararao Jujjuri jv...@linux.vnet.ibm.com
---
hw/virtio-9p.c |6 +-
hw/virtio-9p.h |6 ++
2 files changed, 11
From: Sripathi Kodi sripat...@in.ibm.com
This patch implements the server part of readdir() implementation for
9p2000.L
SYNOPSIS
size[4] Treaddir tag[2] fid[4] offset[8] count[4]
size[4] Rreaddir tag[2] count[4] data[count]
DESCRIPTION
The readdir request asks the server
From: M. Mohan Kumar mo...@in.ibm.com
Compute iounit based on the host filesystem block size and pass it to
client with open/create response. Also return iounit as statfs's f_bsize
for optimal block size transfers.
Signed-off-by: M. Mohan Kumar mo...@in.ibm.com
Reviewd-by: Sripathi Kodi
From: Sripathi Kodi sripat...@in.ibm.com
Signed-off-by: Sripathi Kodi sripat...@in.ibm.com
In v9fs_remove_post_remove() we currently ignore the error returned by
the previous call to remove() and return an error only if freeing the
fid fails. However, the client expects to see the error from
From: M. Mohan Kumar mo...@in.ibm.com
Implement statfs support in qemu server based on Sripathi's
initial statfs patch.
Signed-off-by: M. Mohan Kumar mo...@in.ibm.com
Signed-off-by: Sripathi Kodi sripat...@in.ibm.com
Signed-off-by: Venkateswararao Jujjuri jv...@linux.vnet.ibm.com
---
From: M. Mohan Kumar mo...@in.ibm.com
Implement 9p2000.L version of open(LOPEN) interface in qemu 9p server.
For LOPEN, no need to convert the flags to and from 9p mode to VFS mode.
Synopsis:
size[4] Tlopen tag[2] fid[4] mode[4]
size[4] Rlopen tag[2] qid[13] iounit[4]
Current qemu 9p
From: Sripathi Kodi sripat...@in.ibm.com
Currently v9fs_do_utimensat takes a V9fsStat argument and builds
timespec structures. It sets tv_nsec values to 0 by default. Instead
of this it should take struct timespec[2] and pass it down to the
system directly. This will make it more generic and
From: Arun R Bharadwaj a...@linux.vnet.ibm.com
Signed-off-by: Arun R Bharadwaj a...@linux.vnet.ibm.com
Signed-off-by: Venkateswararao Jujjuri jv...@linux.vnet.ibm.com
---
hw/virtio-9p-debug.c | 26
hw/virtio-9p-debug.h |1 -
hw/virtio-9p.c | 115
From: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
We want to add type specific operation during read/write
Signed-off-by: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
Signed-off-by: Venkateswararao Jujjuri jv...@linux.vnet.ibm.com
---
hw/virtio-9p.c | 110
From: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
TXATTRCREATE: Prepare a fid for setting xattr value on a file system object.
size[4] TXATTRCREATE tag[2] fid[4] name[s] attr_size[8] flags[4]
size[4] RXATTRWALK tag[2]
txattrcreate gets a fid pointing to xattr. This fid can later be
used
This patch implements creating a symlink for TSYMLINK request
and responds with RSYMLINK. In the case of error, we return RERROR.
SYNOPSIS
size[4] Tsymlink tag[2] fid[4] name[s] symtgt[s] gid[4]
size[4] Rsymlink tag[2] qid[13]
DESCRIPTION
Create a symbolic link named 'name'
From: M. Mohan Kumar mo...@in.ibm.com
Synopsis
size[4] Tmkdir tag[2] fid[4] name[s] mode[4] gid[4]
size[4] Rmkdir tag[2] qid[13]
Description
mkdir asks the file server to create a directory with given name,
mode and gid. The qid for the new directory is returned with
the
From: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
When making copy of arguments we were doing partial copy
Signed-off-by: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
Signed-off-by: Venkateswararao Jujjuri jv...@linux.vnet.ibm.com
---
vl.c |4 ++--
1 files changed, 2 insertions(+),
From: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
With mapped security mode we use user.virtfs namespace is used
to store the virtFs related attributes. So hide it from user.
Signed-off-by: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
Signed-off-by: Venkateswararao Jujjuri
From: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
TXATTRWALK: Descend a ATTR namespace
size[4] TXATTRWALK tag[2] fid[4] newfid[4] name[s]
size[4] RXATTRWALK tag[2] size[8]
txattrwalk gets a fid pointing to xattr. This fid can later be
used to get read the xattr value. If name is NULL the
From: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
Signed-off-by: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
Signed-off-by: Venkateswararao Jujjuri jv...@linux.vnet.ibm.com
---
hw/file-op-9p.h |1 +
hw/virtio-9p-local.c | 17 +
hw/virtio-9p.c | 25
From: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
We should always use functions which don't follow
symlink on the server
Signed-off-by: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
Signed-off-by: Venkateswararao Jujjuri jv...@linux.vnet.ibm.com
---
hw/virtio-9p-local.c |2 +-
1
From: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
This is equivalent to SM_PASSTHROUGH security model.
The only exception is, failure of privilige operation like chown
are ignored. This makes a passthrough like security model usable
for people who runs kvm as non root
Signed-off-by: Aneesh
From: Sripathi Kodi sripat...@in.ibm.com
This patch applies on top of 9P2000.L patches that we have on the list.
I took a look at how 9P server is handling open() flags in 9P2000.L path.
I think we can do away with the valid_flags() function and simplify the
code. The reasoning is as follows:
From: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
The arguments are wrong. Use qemu_mallocz directly
Signed-off-by: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
Signed-off-by: Venkateswararao Jujjuri jv...@linux.vnet.ibm.com
---
hw/virtio-9p.c |3 +--
1 files changed, 1
Am 02.09.2010 22:27, schrieb Adam Lackorzynski:
Handle smc as an undefined instruction instead of having it wrongly
interpreted as some other one.
Signed-off-by: Adam Lackorzynskia...@os.inf.tu-dresden.de
---
target-arm/translate.c |6 +-
1 files changed, 5 insertions(+), 1
Handle smc as an undefined instruction instead of having it wrongly
interpreted as some other one.
Signed-off-by: Adam Lackorzynski a...@os.inf.tu-dresden.de
---
target-arm/translate.c |7 ++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/target-arm/translate.c
On Thu, Sep 02, 2010 at 11:40:50PM +0200, Adam Lackorzynski wrote:
+case 7:
+/* SMC? */
+if ((insn 0xfff0) == 0xe1600070) {
+goto illegal_op;
+}
+/* bkpt */
This doesn't look right to me. SMC in the ARM encoding is
During bootup, I also see the following error message:
pci :40:00.0: BAR 0 bad alignment 20:
0x00-0x1f
Any idea whats causing this?
AK
_
From: Isaku Yamahata [mailto:yamah...@valinux.co.jp]
To: Adnan Khaleel [mailto:ad...@khaleel.us]
Cc: Cam
From: Jonathan A. Kollasch jakll...@siwenna.kollasch.net
Signed-off-by: Jonathan A. Kollasch jakll...@kollasch.net
---
hw/ide/core.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/hw/ide/core.c b/hw/ide/core.c
index 3651d2b..2fa26f4 100644
--- a/hw/ide/core.c
+++
In case it isn't obvious, git hates me, a lot. I may just give up on
this bug.
Jonathan Kollasch
On Thu Sep 02, 2010 at 23:14:23 +0100, Peter Maydell wrote:
On Thu, Sep 02, 2010 at 11:40:50PM +0200, Adam Lackorzynski wrote:
+case 7:
+/* SMC? */
+if ((insn 0xfff0) == 0xe1600070) {
+goto illegal_op;
+}
+
The config data field on the e500 pci controller is in little endian, so we need
to enable byte swap there.
Signed-off-by: Alexander Graf ag...@suse.de
---
hw/ppce500_pci.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/ppce500_pci.c b/hw/ppce500_pci.c
index
This time around I also included a fix for the shmem compile bug, as my tree
wouldn't compile otherwise.
The following changes since commit cb93bbdd7db92e50ff5e60a346b23df68acae46b:
Blue Swirl (1):
Fix OpenBSD linker warning
are available in the git repository at:
The compile of ivshmem.c on my ppc system breaks with the following error:
ivshmem.c: In function ‘check_shm_size’:
ivshmem.c:356: error: format ‘%ld’ expects type ‘long int’, but argument
4 has type ‘__off64_t’
This patch adds an explicit cast, making printf happy.
On 03.09.2010, at 01:10, Jonathan A. Kollasch wrote:
In case it isn't obvious, git hates me, a lot. I may just give up on
this bug.
Why? Things looked pretty good except for the subject line/content mess. When
writing a patch, just make sure to have the subject be in the first line of the
Fill in word 64 of IDENTIFY data to indicate support for PIO modes 3 and 4.
This allows NetBSD guests to use UltraDMA modes instead of just PIO mode 0.
---
hw/ide/core.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/hw/ide/core.c b/hw/ide/core.c
index
Hi,
Is my guess that it's the bswapXX functions and not the bswap_XX
functions that are supposed to be used outside of bswap.[ch]?
Jonathan Kollasch
I am currently working on QEMU emulating Linux/SPARC.
I have compiled QEMU-0.12.5 and downloaded sparc-test-0.2.tar.gz
from qemu.org website.
When I have executed “qemu-g” which boots Linux/SPARC, the window
appears but finally it generates the following error.
On Mon, Aug 30, 2010 at 11:32:01AM +0900, Isaku Yamahata wrote:
old_addr is initialized, but not used.
remove the useless variable.
Signed-off-by: Isaku Yamahata yamah...@valinux.co.jp
Thanks.
-Kevin
(2010/08/31 1:58), Cam Macdonell wrote:
fixes gcc 4.1 warning
Signed-off-by: Cam Macdonell c...@cs.ualberta.ca
---
hw/ivshmem.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/ivshmem.c b/hw/ivshmem.c
index bbb5cba..fa9c684 100644
--- a/hw/ivshmem.c
+++
fixes gcc 4.1 warning:
In function 'ivshmem_io_writel':
202: warning: comparison is always false due to limited range of data type
208: warning: comparison is always true due to limited range of data type
Signed-off-by: Hidetoshi Seto seto.hideto...@jp.fujitsu.com
---
hw/ivshmem.c |4 ++--
On Thu, Sep 02, 2010 at 12:42:42PM -0500, Adnan Khaleel wrote:
I've tried everything you mentioned and I still get the same problem. The only
thing that seems to avoid that issue is if I reduce the aperture size from
0x20ull to 0x200ull.
I suppose that Cam is seeing the same issue.
On Sat, Aug 28, 2010 at 06:02:55PM +0300, Eduard - Gabriel Munteanu wrote:
The conversion was done using the GNU 'expand' tool (default settings)
to make it obey the SeaBIOS coding style.
Signed-off-by: Eduard - Gabriel Munteanu eduard.munte...@linux360.ro
Thanks Eduard.
Patch 1 - I don't
Given the usage of 3/4, u32 pci_find_capability(bdf, cap) would be more direct.
Maybe this is a matter of taste, though.
On Sat, Aug 28, 2010 at 06:02:56PM +0300, Eduard - Gabriel Munteanu wrote:
This iterates over capabilities exposed by PCI devices. It's needed by
IOMMU initialization code
How about the following approach?
Although I'm not sure how much multiple iommus is wanted,
it wouldn't pose single iommu limit and global variables in 3/4
would be unnecessary.
In stead of ACPI_INIT_TABLE(build_ivrs()),
something like
foreachpci() {
if (class ==
I think those global variables are unnecessary.
Please see the comment on 4/4.
thanks,
On Sat, Aug 28, 2010 at 06:02:57PM +0300, Eduard - Gabriel Munteanu wrote:
The AMD IOMMU must be discovered and initialized by the BIOS if present.
Signed-off-by: Eduard - Gabriel Munteanu
(2010/09/03 10:54), Hidetoshi Seto wrote:
fixes gcc 4.1 warning:
In function 'ivshmem_io_writel':
202: warning: comparison is always false due to limited range of data type
208: warning: comparison is always true due to limited range of data type
Signed-off-by: Hidetoshi Seto
On Thu, Sep 2, 2010 at 6:41 PM, Andrea Galeazzi galea...@korg.it wrote:
Hi every body,
I'm a newbie about the qemu word but I'd like to emulate the versatile ARM
platform. In particular I'm very interested in knowing how much the
emulation of PL110 LCD controller fits the real hardware. Are
70 matches
Mail list logo
