I'm now implementing the support for creating a rootstock rootfs without
requiring root, and I also got stuck at a segmentation fault, just after
executing the debootstrap' second stage.
I'm running the qemu-system-arm from qemu-kvm-extras 0.12.4+noroms-
0ubuntu4, at maverick.
My qemu command lin
On 07/11/2010 11:24 PM, Alex Williamson wrote:
One other thing to be aware of is that vfio requires devices to be
PCI-2.3 compliant in order to support DisINTx. This allows vfio to
support devices making use of shared INTx interrupts, but excludes older
devices that users maybe managed to get a
On 07/11/2010 09:30 PM, Avi Kivity wrote:
Registering an eventfd for the eoi seems like a reasonable alternative.
I'm worried about that racing (with what?)
I don't think there's a problem.
First, the EOI message is itself asynchronous. While the write to the
local APIC is synchronous, eff
On 07/11/2010 10:38 PM, Alex Williamson wrote:
What
about page attributes?
There are two cases:
- snoop capable iommu - can use write-backed RAM, but need to enable
snoop. BARs still need to respect page attributes.
- older mmu - need to respect guest memory type; probably cannot be done
wit
Add support for the following missing priviledged intructions:
For SH4:
- stc sgr, Rn
- stc.l sgr, @-Rn
For SH4A:
- ldc Rm, sgr
- ldc.l @Rm+, sgr
Signed-off-by: Alexandre Courbot
---
target-sh4/translate.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/target-sh4/tra
The LDST macro is used to generate ldc and stc instructions that work with a
specific register. However, the SGR register only supports stc up to SH4A,
which supports both stc and ldc. This patch creates two sub-macros named LD
and ST that handle generating ldc and stc instructions separately, and
This series of patch adds support for the missing ldc & stc privileged
instructions with the sgr register. In order to take the difference
of support between SH4A and SH4 (which does not recognize ldc with sgr),
the LDST macro has been split into two simpler macros.
Changelog from v1: signed off t
[PATCH] Separate monitor command handler interfaces and tracing internals.
Changelog from v3:
- cleanup ( removed unnecessary references to 'rec' )
Signed-off-by: Prerna Saxena
---
monitor.c | 23 +++
simpletrace.c | 50 --
On Sun, 2010-07-11 at 23:12 +0300, Michael S. Tsirkin wrote:
> On Sun, Jul 11, 2010 at 02:03:34PM -0600, Alex Williamson wrote:
> > > What about threaded interrupts?
>
> Just to make the point, imagine a nested virt situation
> which uses current kvm device assignment in guest.
> Look at the inter
A couple of pci fixes in vmware are untested, but look
very minor to me and no one objected yet - let's merge and
handle the fallout if any.
The following changes since commit 1ddda5cd364d2f82201830ca69675e17c60ded8e:
AppleSMC device emulation (2010-07-11 20:33:10 +0300)
are available in the g
On Sun, 2010-07-11 at 21:43 +0300, Avi Kivity wrote:
> On 07/11/2010 09:37 PM, Alex Williamson wrote:
> > On Sun, 2010-07-11 at 21:17 +0300, Avi Kivity wrote:
> >
> >> On 07/11/2010 09:09 PM, Alex Williamson wrote:
> >>
> >>> The following series implements QEMU device assignment using th
On Sun, Jul 11, 2010 at 02:03:34PM -0600, Alex Williamson wrote:
> > What about threaded interrupts?
Just to make the point, imagine a nested virt situation
which uses current kvm device assignment in guest.
Look at the interrupt handler we have there.
--
Alex
On Sun, Jul 11, 2010 at 02:03:34PM -0600, Alex Williamson wrote:
> On Sun, 2010-07-11 at 22:23 +0300, Michael S. Tsirkin wrote:
> > On Sun, Jul 11, 2010 at 01:21:18PM -0600, Alex Williamson wrote:
> > > On Sun, 2010-07-11 at 21:54 +0300, Michael S. Tsirkin wrote:
> > > > On Sun, Jul 11, 2010 at 09:
On Sun, 2010-07-11 at 22:23 +0300, Michael S. Tsirkin wrote:
> On Sun, Jul 11, 2010 at 01:21:18PM -0600, Alex Williamson wrote:
> > On Sun, 2010-07-11 at 21:54 +0300, Michael S. Tsirkin wrote:
> > > On Sun, Jul 11, 2010 at 09:30:59PM +0300, Avi Kivity wrote:
> > > > On 07/11/2010 09:26 PM, Alex Wil
On Sun, 2010-07-11 at 21:27 +0300, Avi Kivity wrote:
> On 07/11/2010 09:09 PM, Alex Williamson wrote:
> > This patch adds qemu device assignment support using the proposed
> > VFIO/UIOMMU kernel interfaces. The existing KVM-only device assignment
> > code makes use of various pci sysfs files for c
Thanks, applied.
On Sun, Jul 11, 2010 at 7:15 AM, Alexander Graf wrote:
>
> On 30.06.2010, at 10:41, Alexander Graf wrote:
>
>> Intel Macs have a chip called the "AppleSMC" which they use to control
>> certain Apple specific parts of the hardware, like the keyboard background
>> light.
>>
>> That
On Sun, Jul 11, 2010 at 01:21:18PM -0600, Alex Williamson wrote:
> On Sun, 2010-07-11 at 21:54 +0300, Michael S. Tsirkin wrote:
> > On Sun, Jul 11, 2010 at 09:30:59PM +0300, Avi Kivity wrote:
> > > On 07/11/2010 09:26 PM, Alex Williamson wrote:
> > > >On Sun, 2010-07-11 at 21:14 +0300, Avi Kivity w
Thanks, applied.
On Sun, Jul 11, 2010 at 4:34 PM, Stefan Weil wrote:
> rewuired -> required
> ths -> this
>
> Signed-off-by: Stefan Weil
> ---
> qemu-doc.texi | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/qemu-doc.texi b/qemu-doc.texi
> index e2c8e56..e67
Thanks, applied.
2010/7/8 Hidetoshi Seto :
> So interpret it by hand.
>
> Signed-off-by: Hidetoshi Seto
> ---
> Makefile | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 7b82a33..6fc1b2c 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -171
Thanks, applied.
2010/7/8 Hidetoshi Seto :
> There were fsdev/qemu-fsdev.{o,d} not removed at "make clean".
>
> Signed-off-by: Hidetoshi Seto
> ---
> Makefile | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 560eac6..7b82a33 100644
> ---
Thanks, applied all.
On Fri, Jul 9, 2010 at 1:44 AM, Isaku Yamahata wrote:
> Ping?
> Since this is bug fix patches, I'd like to include them
> into the next release.
>
> On Wed, Jun 23, 2010 at 04:15:24PM +0900, Isaku Yamahata wrote:
>> Maing changes v4 -> v5:
>> - split up/reorder patches for bi
On Sun, 2010-07-11 at 21:54 +0300, Michael S. Tsirkin wrote:
> On Sun, Jul 11, 2010 at 09:30:59PM +0300, Avi Kivity wrote:
> > On 07/11/2010 09:26 PM, Alex Williamson wrote:
> > >On Sun, 2010-07-11 at 21:14 +0300, Avi Kivity wrote:
> > >>On 07/11/2010 09:09 PM, Alex Williamson wrote:
> > >>>For dev
On Sun, Jul 11, 2010 at 09:30:59PM +0300, Avi Kivity wrote:
> On 07/11/2010 09:26 PM, Alex Williamson wrote:
> >On Sun, 2010-07-11 at 21:14 +0300, Avi Kivity wrote:
> >>On 07/11/2010 09:09 PM, Alex Williamson wrote:
> >>>For device assignment, we need to know when the VM writes an end
> >>>of inter
On 07/11/2010 09:37 PM, Alex Williamson wrote:
On Sun, 2010-07-11 at 21:17 +0300, Avi Kivity wrote:
On 07/11/2010 09:09 PM, Alex Williamson wrote:
The following series implements QEMU device assignment using the
proposed VFIO/UIOMMU kernel interfaces. See the last patch for
further v
On Sun, 2010-07-11 at 21:17 +0300, Avi Kivity wrote:
> On 07/11/2010 09:09 PM, Alex Williamson wrote:
> > The following series implements QEMU device assignment using the
> > proposed VFIO/UIOMMU kernel interfaces. See the last patch for
> > further vfio description. I've tested this on the v2 VF
On 07/11/2010 09:26 PM, Alex Williamson wrote:
On Sun, 2010-07-11 at 21:14 +0300, Avi Kivity wrote:
On 07/11/2010 09:09 PM, Alex Williamson wrote:
For device assignment, we need to know when the VM writes an end
of interrupt to the APIC, which allows us to de-assert the interrupt
line
On 07/11/2010 09:09 PM, Alex Williamson wrote:
This patch adds qemu device assignment support using the proposed
VFIO/UIOMMU kernel interfaces. The existing KVM-only device assignment
code makes use of various pci sysfs files for config space, MMIO BAR
mapping, and misc other config items. It t
On 07/11/2010 09:24 PM, Alex Williamson wrote:
Really? Looks like new code.
Yeah, I just stole the copyright Anthony used for this file.
Traditionally, one steals the code and updates the attributions, not the
other way round.
--
I have a truly marvellous patch that fixes
On Sun, 2010-07-11 at 21:14 +0300, Avi Kivity wrote:
> On 07/11/2010 09:09 PM, Alex Williamson wrote:
> > For device assignment, we need to know when the VM writes an end
> > of interrupt to the APIC, which allows us to de-assert the interrupt
> > line and clear the DisINTx bit. Add a new wrapper
On Sun, 2010-07-11 at 21:20 +0300, Avi Kivity wrote:
> On 07/11/2010 09:09 PM, Alex Williamson wrote:
> > This adds a minimum chunk of Anthony's RAM API support so that we
> > can identify actual VM RAM versus all the other things that make
> > use of qemu_ram_alloc.
> >
> > typedef void CPUWrite
On 07/11/2010 09:09 PM, Alex Williamson wrote:
The following series implements QEMU device assignment using the
proposed VFIO/UIOMMU kernel interfaces. See the last patch for
further vfio description. I've tested this on the v2 VFIO patch,
with a number of fixes hacked in along the way. I'll u
On 07/11/2010 09:09 PM, Alex Williamson wrote:
This adds a minimum chunk of Anthony's RAM API support so that we
can identify actual VM RAM versus all the other things that make
use of qemu_ram_alloc.
typedef void CPUWriteMemoryFunc(void *opaque, target_phys_addr_t addr,
uint32_t value);
diff
On Sun, 2010-07-11 at 12:09 -0600, Alex Williamson wrote:
> This adds a minimum chunk of Anthony's RAM API support so that we
> can identify actual VM RAM versus all the other things that make
> use of qemu_ram_alloc.
>
> Signed-off-by: Alex Williamson
Oops, I'm making up email address now ;)
S
This patch adds qemu device assignment support using the proposed
VFIO/UIOMMU kernel interfaces. The existing KVM-only device assignment
code makes use of various pci sysfs files for config space, MMIO BAR
mapping, and misc other config items. It then jumps over to KVM-specific
ioctls for enablin
On 07/11/2010 09:09 PM, Alex Williamson wrote:
For device assignment, we need to know when the VM writes an end
of interrupt to the APIC, which allows us to de-assert the interrupt
line and clear the DisINTx bit. Add a new wrapper for ioapic
generated interrupts with a callback on eoi and create
The following series implements QEMU device assignment using the
proposed VFIO/UIOMMU kernel interfaces. See the last patch for
further vfio description. I've tested this on the v2 VFIO patch,
with a number of fixes hacked in along the way. I'll update when
Tom releases a new version of VFIO. H
For device assignment, we need to know when the VM writes an end
of interrupt to the APIC, which allows us to de-assert the interrupt
line and clear the DisINTx bit. Add a new wrapper for ioapic
generated interrupts with a callback on eoi and create an interface
for drivers to be notified on eoi.
Register the actual VM RAM using the new API
Signed-off-by: Alex Williamson
---
hw/pc.c | 12 ++--
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/hw/pc.c b/hw/pc.c
index a96187f..b9ce6ae 100644
--- a/hw/pc.c
+++ b/hw/pc.c
@@ -911,13 +911,13 @@ void pc_memory_init(ram_a
This adds a minimum chunk of Anthony's RAM API support so that we
can identify actual VM RAM versus all the other things that make
use of qemu_ram_alloc.
Signed-off-by: Alex Williamson
---
Makefile.target |1 +
cpu-common.h|2 +
memory.c| 77 +++
For assigned devices, we want to map the PCI BARs into the VM
address space. This is just like mapping an option ROM except
the host backing is an mmap area instead of a chunk of vmalloc
memory. This allow registration and removal of such areas.
Signed-off-by: Alex Williamson
---
cpu-common.h
On Fri, Jul 09, 2010 at 08:30:07PM +0200, Stefan Weil wrote:
> Replace rebase by resize in documentation of resize command.
>
> Cc: Stefan Hajnoczi
> Cc: Kevin Wolf
>
> Signed-off-by: Stefan Weil
> ---
Looks good, thanks for fixing this.
Stefan
> qemu-img-cmds.hx |2 +-
> 1 files chang
rewuired -> required
ths -> this
Signed-off-by: Stefan Weil
---
qemu-doc.texi |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/qemu-doc.texi b/qemu-doc.texi
index e2c8e56..e67bf44 100644
--- a/qemu-doc.texi
+++ b/qemu-doc.texi
@@ -2138,8 +2138,8 @@ Set the x86 sta
On 30.06.2010, at 10:41, Alexander Graf wrote:
> Intel Macs have a chip called the "AppleSMC" which they use to control
> certain Apple specific parts of the hardware, like the keyboard background
> light.
>
> That chip is also used to store a key that Mac OS X uses to decrypt binaries.
>
> Thi
43 matches
Mail list logo
