search for: ioport

...int32_t s/parsion/parsing/ diff -r ccbee5bcb31b -r ddde6c2c45de docs/man/xl.cfg.pod.5 --- a/docs/man/xl.cfg.pod.5 Fri Aug 31 12:03:55 2012 +0100 +++ b/docs/man/xl.cfg.pod.5 Fri Aug 31 16:54:01 2012 +0100 @@ -402,6 +402,30 @@ for more information on the "permissive" =back +=item B<ioports=[ "IOPORT_RANGE", "IOPORT_RANGE", ... ]> + +=over 4 + +Allow guest to access specific legacy I/O ports. Each B<IOPORT_RANGE> +is given in hexadecimal and may either a span e.g. C<2f8-2ff> +(inclusive) or a single I/O port C<2f8>. + +It is recommended to use...

...+ return security_iterate_iomem_sids(start, end, _iomem_has_perm, &data); } static int flask_perfcontrol(void) @@ -736,45 +741,49 @@ static int flask_shadow_control(struct domain *d, uint32_t op) return domain_has_perm(current->domain, d, SECCLASS_SHADOW, perm); } -static int ioport_has_perm(struct domain *d, uint32_t ioport, uint8_t access) -{ +struct ioport_has_perm_data { + struct domain_security_struct *ssec, *tsec; u32 perm; - u32 rsid; - int rc = -EPERM; +}; +static int _ioport_has_perm(void *v, u32 sid, unsigned long start, unsigned long end) +{ + str...

...ion of enumerator 'true' include/linux/stddef.h:18: error: previous definition of 'true' was here drivers/scsi/BusLogic.c: In function 'BusLogic_InitializeProbeInfoListISA': drivers/scsi/BusLogic.c:584: warning: 'check_region' is deprecated (declared at include/linux/ioport.h:134) drivers/scsi/BusLogic.c:586: warning: 'check_region' is deprecated (declared at include/linux/ioport.h:134) drivers/scsi/BusLogic.c:588: warning: 'check_region' is deprecated (declared at include/linux/ioport.h:134) drivers/scsi/BusLogic.c:590: warning: 'check_region'...

qxl has two modes: "native" (used by the drm driver) and "vga" (vga compatibility mode, typically used for boot display and firmware framebuffers). Accessing any vga ioport will switch the qxl device into vga mode. The qxl driver never does that, but other drivers accessing vga ports can trigger that too and therefore disturb qxl operation. So aquire the legacy vga ioports from vgaarb to avoid that. Reproducer: Boot kvm guest with both qxl and i915 vgpu, with qxl be...

Hello, I am creating a domU with Ubuntu12.04, I need to provide dom0''s certain ioports(0xcd0-0xcdb) to domU. I have added *ioports = [ "cd0-cdb" ] *and tried it in the domU, its been not mapped on domU. On host I am using xen-4.2 and tool stack xl. Let me know if I have to add anymore information to config file to grant access to domU ______________________________...

...ic Biederman <ebiederm at xmission.com> > Cc: Thomas Gleixner <tglx at linutronix.de> > Cc: Greg Kroah-Hartman <gregkh at linuxfoundation.org> > Cc: kexec at lists.infradead.org > Signed-off-by: David Hildenbrand <david at redhat.com> > --- > include/linux/ioport.h | 4 +++- > kernel/kexec_file.c | 2 +- > mm/memory_hotplug.c | 4 ++-- > 3 files changed, 6 insertions(+), 4 deletions(-) > > diff --git a/include/linux/ioport.h b/include/linux/ioport.h > index 52a91f5fa1a36..d7620d7c941a0 100644 > --- a/include/linux/ioport.h > +...

With this patch, x86 and x86-64 share ioport.c, fixing LTP iopl and ioperm testcase failures (on both). We found an iopl testcase failing even on x86 xenlinux. Now x86-64 xenlinux should have the same results regarding the LTP testcases (as far as we tested). Signed-off-by: Li B Xin <li.b.xin@intel.com> Signed-off-by: Jun Nakajima &lt...

...d off by Matthew Fioravante: matthew.fioravante@jhuapl.edu --- Changes from previous * Rebased onto latest xen-unstable * Rewrote the feature to mimic the style used by iports and irqs in current libxl * Updated xl.cfg manpage * removed the redundant "allow" field, its not used by irq or ioports either. * fixed whitespace errors diff --git a/docs/man/xl.cfg.pod.5 b/docs/man/xl.cfg.pod.5 --- a/docs/man/xl.cfg.pod.5 +++ b/docs/man/xl.cfg.pod.5 @@ -496,6 +496,16 @@ is given in hexadecimal and may either a span e.g. C<2f8-2ff> It is recommended to use this option only for trusted VMs...

...e stock packages from Centos 5.5 ( fully updated) and also with gitco's 3.4.3 but after 2 days of googling and testing we still fail to access the serial interface from DomU. No matter what we've tried, - in DomU there is no reference to any kind of serial ports in /proc/{interrupts,ioports} - the test program which accesses ttyS0 fails ( it works just fine in dom0) even after manually loading parport_serial in DomU /dev/ttyS{0..3} do get created by default, if that matters. Here is the content of the config file, after the last attempt (which uses gitco's xen, bu...

Hello, I''m working on a project and trying to pass through a PS/2 mouse + keyboard to a hardware VM. I''ve played with numerous things (including the obvious, using USB), but after finding no alternative, it seems like the best way to approach this would be to modify qemu-dm to pipe through data from /dev/input/eventwhatever to the keyboard/mouse that qemu provides (and then

qxl has two modes: "native" (used by the drm driver) and "vga" (vga compatibility mode, typically used for boot display and firmware framebuffers). Accessing any vga ioport will switch the qxl device into vga mode. The qxl driver never does that, but other drivers accessing vga ports can trigger that too and therefore disturb qxl operation. So aquire the legacy vga ioports from vgaarb to avoid that. Reporducer: Boot kvm guest with both qxl and i915 vgpu, with qxl be...

> > qxl has two modes: "native" (used by the drm driver) and "vga" (vga > compatibility mode, typically used for boot display and firmware > framebuffers). > > Accessing any vga ioport will switch the qxl device into vga mode. > The qxl driver never does that, but other drivers accessing vga ports > can trigger that too and therefore disturb qxl operation. So aquire > the legacy vga ioports from vgaarb to avoid that. > > Reporducer: Boot kvm guest with both qxl a...

...insmoded them in a domU. I used this example "http://www.faqs.org/docs/kernel/x1206.html". With pci-access to the pci/isa-bridge it seems to work. But the problem is, the scancode from the example "scancode = inb(0x60);" is always "ffffffff". Can I access to this ioport from domU. I think its possible, because "cat /proc/ioports" shows an port"0060-006f : keyboard". Best regards Tino _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I notice that xen 3.3 actually makes use of the ioport range in the platform pci device. Under xen 3.2 I created a little patch to dump log output via writes to that ioport range. Is that something that could be considered for inclusion into 3.3 too? Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists...

I configured a domU to access to the physical serial port of the dom0 (/dev/ttyS0) typing this in the domU configuration file: irq = [ 4 ] ioports = [ "3f8-3ff" ] The domU starts without any error, but the serial port isn''t recognised. The /dev/ttyS0 device exists on the domU, and I blacklisted the serial_core, the 8250 and 8250_pnp modules on the dom0. What is the problem? Could you help me, please? Thank you very much...

...0:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:41 memory:f0000000-f03fffff memory:e0000000-efffffff ioport:5000(size=64) *-communication:0 description: Communication controller product: Cougar Point HECI Controller #1 vendor: Intel Corporation physical id: 16 bus info: pci at 0000:00:16.0 version: 04...

...at 0000:00:02.0 version: 0c width: 32 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:115 memory:50000000-503fffff memory:40000000-4fffffff ioport:2050(size=8) *-generic:0 description: SD Host controller product: Atom Processor Z36xxx/Z37xxx Series SDIO Controller vendor: Intel Corporation physical id: 12 bus info: pci at 0000:00:12.0 version: 0c...

.../19 2:43 AM, Christoph Hellwig wrote: > Keep the physical address allocation that hmm_add_device does with the > rest of the resource code, and allow future reuse of it without the hmm > wrapper. > > Signed-off-by: Christoph Hellwig <hch at lst.de> > --- > include/linux/ioport.h | 2 ++ > kernel/resource.c | 39 +++++++++++++++++++++++++++++++++++++++ > mm/hmm.c | 33 ++++----------------------------- > 3 files changed, 45 insertions(+), 29 deletions(-) Some trivial typos noted below, but this accurately moves the code into a helper routine,...

...is Freeing initrd memory: 6485k freed NET: Registered protocol family 16 No dock devices found. ACPI: bus type pci registered PCI: Using MMCONFIG at e0000000 PCI: Dell PowerEdge 1950 detected, enabling pci=bfsort. ACPI: Interpreter enabled ACPI: UsingPCI-GART: No AMD northbridge found. pnp: 00:08: ioport range 0x800-0x87f could not be reserved pnp: 00:08: ioport range 0x880-0x8bf has been reserved pnp: 00:08: ioport range 0x8c0-0x8df has been reserved pnp: 00:08: ioport range 0x8e0-0x8e3 has been reserved pnp: 00:08: ioport range 0x900-0x900 has been reserved pnp: 00:08: ioport range 0xc00-0xc7f ha...

...operm(gfx_info.host_pio_base, gfx_info.pio_size, 1); asm volatile ("out %1, %0"::"Nd"(hport),"a"(data)); ioperm(gfx_info.host_pio_base, gfx_info.pio_size, 0); } I tried old 2.6.32 XEN kernel and there is no such problem. It looks related to arch/x86/kernel/ioport.c but I''m not sure. Is anyone here familiar with that code? -- Pavel Mateja _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel