Displaying 8 results from an estimated 8 matches for "memory_region_add_subregion".
2020 Mar 02
2
[PATCH] drm/bochs: Remove vga write
...t; - memory_region_init(&s->mmio, obj, "bochs-display-mmio",
> - PCI_VGA_MMIO_SIZE);
> + memory_region_init_io(&s->mmio, obj, &dummy_ops, NULL,
> + "bochs-display-mmio", PCI_VGA_MMIO_SIZE);
> memory_region_add_subregion(&s->mmio, PCI_VGA_BOCHS_OFFSET, &s->vbe);
> memory_region_add_subregion(&s->mmio, PCI_VGA_QEXT_OFFSET, &s->qext);
>
>
2020 Mar 02
2
[PATCH] drm/bochs: Remove vga write
...t; - memory_region_init(&s->mmio, obj, "bochs-display-mmio",
> - PCI_VGA_MMIO_SIZE);
> + memory_region_init_io(&s->mmio, obj, &dummy_ops, NULL,
> + "bochs-display-mmio", PCI_VGA_MMIO_SIZE);
> memory_region_add_subregion(&s->mmio, PCI_VGA_BOCHS_OFFSET, &s->vbe);
> memory_region_add_subregion(&s->mmio, PCI_VGA_QEXT_OFFSET, &s->qext);
>
>
2012 Oct 08
21
[PATCH 00/14] Remove old_portio users for memory region PIO mapping
When running on PowerPC, we don''t have native PIO support. There are a few hacks
around to enable PIO access on PowerPC nevertheless.
The most typical one is the isa-mmio device. It takes MMIO requests and converts
them to PIO requests on the (QEMU internal) PIO bus.
This however is not how real hardware works and it limits us in the ability to
spawn eventfd''s on PIO ports
2013 May 28
3
[PATCH RFC] virtio-pci: new config layout: using memory BAR
...unsigned offset,
+ unsigned size,
+ unsigned cap_type,
+ unsigned cap_length)
+{
+ struct virtio_pci_cap *cap;
+ int c;
+ memory_region_init_io(reg, ops, proxy, name, size);
+ memory_region_add_subregion(&proxy->config_bar, offset, reg);
+
+ if (!cap_length) {
+ cap_length = sizeof *cap;
+ }
+ c = pci_add_capability(&proxy->pci_dev, PCI_CAP_ID_VNDR, 0, cap_length);
+ assert(c > 0);
+ cap = (void *)proxy->pci_dev.config + c;
+ cap->cap_length = cap_len...
2013 May 28
3
[PATCH RFC] virtio-pci: new config layout: using memory BAR
...unsigned offset,
+ unsigned size,
+ unsigned cap_type,
+ unsigned cap_length)
+{
+ struct virtio_pci_cap *cap;
+ int c;
+ memory_region_init_io(reg, ops, proxy, name, size);
+ memory_region_add_subregion(&proxy->config_bar, offset, reg);
+
+ if (!cap_length) {
+ cap_length = sizeof *cap;
+ }
+ c = pci_add_capability(&proxy->pci_dev, PCI_CAP_ID_VNDR, 0, cap_length);
+ assert(c > 0);
+ cap = (void *)proxy->pci_dev.config + c;
+ cap->cap_length = cap_len...
2013 May 28
0
[PATCH RFC] virtio-pci: new config layout: using memory BAR
...+ unsigned size,
> + unsigned cap_type,
> + unsigned cap_length)
> +{
> + struct virtio_pci_cap *cap;
> + int c;
> + memory_region_init_io(reg, ops, proxy, name, size);
> + memory_region_add_subregion(&proxy->config_bar, offset, reg);
> +
> + if (!cap_length) {
> + cap_length = sizeof *cap;
> + }
> + c = pci_add_capability(&proxy->pci_dev, PCI_CAP_ID_VNDR, 0, cap_length);
> + assert(c > 0);
> + cap = (void *)proxy->pci_dev.config + c...
2015 Oct 26
9
[PATCH 0/7] Hyper-V Synthetic interrupt controller
Hyper-V SynIC (synthetic interrupt controller) device
implementation.
The implementation contains:
* msr's support
* irq routing setup
* irq injection
* irq ack callback registration
* event/message pages changes tracking at Hyper-V exit
* Hyper-V test device to test SynIC by kvm-unit-tests
Andrey Smetanin (7):
standard-headers/x86: add Hyper-V SynIC constants
target-i386/kvm: Hyper-V
2015 Oct 26
9
[PATCH 0/7] Hyper-V Synthetic interrupt controller
Hyper-V SynIC (synthetic interrupt controller) device
implementation.
The implementation contains:
* msr's support
* irq routing setup
* irq injection
* irq ack callback registration
* event/message pages changes tracking at Hyper-V exit
* Hyper-V test device to test SynIC by kvm-unit-tests
Andrey Smetanin (7):
standard-headers/x86: add Hyper-V SynIC constants
target-i386/kvm: Hyper-V