Displaying 6 results from an estimated 6 matches for "smram".
Did you mean:
scram
2015 Jul 28
2
[PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
...> Adding interrupt remapping will require a new chipset and/or a hack
> switch to ignore compatibility.
Isn't the VT-d register space separate from other Q35 features and
backwards-compatible? You could even add it to PIIX in theory just by
adding a DMAR.
It's not like for example SMRAM, where the registers are in the
northbridge configuration space and move around in every chipset generation.
> > ("Any kind of stability" actually didn't include crashes; those are not
> > expected :))
> >
> > The Google patches for userspace PIC and IOAPIC a...
2015 Jul 28
2
[PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
...> Adding interrupt remapping will require a new chipset and/or a hack
> switch to ignore compatibility.
Isn't the VT-d register space separate from other Q35 features and
backwards-compatible? You could even add it to PIIX in theory just by
adding a DMAR.
It's not like for example SMRAM, where the registers are in the
northbridge configuration space and move around in every chipset generation.
> > ("Any kind of stability" actually didn't include crashes; those are not
> > expected :))
> >
> > The Google patches for userspace PIC and IOAPIC a...
2015 Jul 28
0
[PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
...register space separate from other Q35 features and
> backwards-compatible? You could even add it to PIIX in theory just by
> adding a DMAR.
Yes, it's practically working, but it's not accurate /wrt how that
hardware looked like in reality.
>
> It's not like for example SMRAM, where the registers are in the
> northbridge configuration space and move around in every chipset generation.
>
>>> ("Any kind of stability" actually didn't include crashes; those are not
>>> expected :))
>>>
>>> The Google patches for users...
2015 Jul 28
2
[PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
On 28/07/2015 15:11, Jan Kiszka wrote:
>>> >>
>>> >> This doesn't matter much, since the only guests that implement an IOMMU
>>> >> in QEMU are (afaik) PPC and x86, and x86 does not yet promise any kind
>>> >> of stability.
>> >
>> > Hmm I think Jan (cc) said it was already used out there.
> Yes, no known issues
2015 Jul 28
2
[PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
On 28/07/2015 15:11, Jan Kiszka wrote:
>>> >>
>>> >> This doesn't matter much, since the only guests that implement an IOMMU
>>> >> in QEMU are (afaik) PPC and x86, and x86 does not yet promise any kind
>>> >> of stability.
>> >
>> > Hmm I think Jan (cc) said it was already used out there.
> Yes, no known issues
2010 Aug 12
59
[PATCH 00/15] RFC xen device model support
Hi all,
this is the long awaited patch series to add xen device model support in
qemu; the main author is Anthony Perard.
Developing this series we tried to come up with the cleanest possible
solution from the qemu point of view, limiting the amount of changes to
common code as much as possible. The end result still requires a couple
of hooks in piix_pci but overall the impact should be very