Displaying 20 results from an estimated 4000 matches similar to: "[PATCH 7/7] [v4] drivers/virt: introduce Freescale hypervisor management driver"
2011 Jun 09
2
[PATCH 7/7] [v5] drivers/virt: introduce Freescale hypervisor management driver
Add the drivers/virt directory, which houses drivers that support
virtualization environments, and add the Freescale hypervisor management
driver.
The Freescale hypervisor management driver provides several services to
drivers and applications related to the Freescale hypervisor:
1. An ioctl interface for querying and managing partitions
2. A file interface to reading incoming doorbells
3. An
2011 Jun 09
2
[PATCH 7/7] [v5] drivers/virt: introduce Freescale hypervisor management driver
Add the drivers/virt directory, which houses drivers that support
virtualization environments, and add the Freescale hypervisor management
driver.
The Freescale hypervisor management driver provides several services to
drivers and applications related to the Freescale hypervisor:
1. An ioctl interface for querying and managing partitions
2. A file interface to reading incoming doorbells
3. An
2011 Jun 09
1
[PATCH 7/7] [v6] drivers/virt: introduce Freescale hypervisor management driver
Add the drivers/virt directory, which houses drivers that support
virtualization environments, and add the Freescale hypervisor management
driver.
The Freescale hypervisor management driver provides several services to
drivers and applications related to the Freescale hypervisor:
1. An ioctl interface for querying and managing partitions
2. A file interface to reading incoming doorbells
3. An
2011 Jun 09
1
[PATCH 7/7] [v6] drivers/virt: introduce Freescale hypervisor management driver
Add the drivers/virt directory, which houses drivers that support
virtualization environments, and add the Freescale hypervisor management
driver.
The Freescale hypervisor management driver provides several services to
drivers and applications related to the Freescale hypervisor:
1. An ioctl interface for querying and managing partitions
2. A file interface to reading incoming doorbells
3. An
2014 Jun 10
2
Re: libguestfs supermin error
Hi Rich
I'm able to solve the problem regarding PAPR in libguestfs on my powerpc
ubuntu.By default the libguestfs was configuring pseries machine and
afterwards I changed it to my original machine i.e ppce500 .The changes are
performed in ./src/guestfs-internal.h file.
Thanks
On Tue, Jun 10, 2014 at 7:58 PM, Richard W.M. Jones <rjones@redhat.com>
wrote:
> On Wed, Jun 04, 2014 at
2013 Jul 02
7
RFC: vfio interface for platform devices
The write-up below is the first draft of a proposal for how the kernel can expose
platform devices to user space using vfio.
In short, I'm proposing a new ioctl VFIO_DEVICE_GET_DEVTREE_INFO which
allows user space to correlate regions and interrupts to the corresponding
device tree node structure that is defined for most platform devices.
Regards,
Stuart Yoder
2013 Jul 02
7
RFC: vfio interface for platform devices
The write-up below is the first draft of a proposal for how the kernel can expose
platform devices to user space using vfio.
In short, I'm proposing a new ioctl VFIO_DEVICE_GET_DEVTREE_INFO which
allows user space to correlate regions and interrupts to the corresponding
device tree node structure that is defined for most platform devices.
Regards,
Stuart Yoder
2014 Jun 11
2
Re: libguestfs supermin error
On Wed, Jun 11, 2014 at 01:00:16PM +0530, abhishek jain wrote:
> Hi RIch
>
> Below are the logs updated logs of libguestfs-test-tool on ubuntu powerpc...
>
> libguestfs-test-tool
> ************************************************************
> * IMPORTANT NOTICE
> *
> * When reporting bugs, include the COMPLETE, UNEDITED
>
2013 Jul 03
6
RFC: vfio interface for platform devices (v2)
Version 2
-VFIO_GROUP_GET_DEVICE_FD-- specified that the path is a sysfs path
-VFIO_DEVICE_GET_INFO-- defined 2 flags instead of 1
-deleted VFIO_DEVICE_GET_DEVTREE_INFO ioctl
-VFIO_DEVICE_GET_REGION_INFO-- updated as per AlexW's suggestion,
defined 5 new flags and associated structs
-VFIO_DEVICE_GET_IRQ_INFO-- updated as per AlexW's suggestion,
defined 1 new flag and
2013 Jul 03
6
RFC: vfio interface for platform devices (v2)
Version 2
-VFIO_GROUP_GET_DEVICE_FD-- specified that the path is a sysfs path
-VFIO_DEVICE_GET_INFO-- defined 2 flags instead of 1
-deleted VFIO_DEVICE_GET_DEVTREE_INFO ioctl
-VFIO_DEVICE_GET_REGION_INFO-- updated as per AlexW's suggestion,
defined 5 new flags and associated structs
-VFIO_DEVICE_GET_IRQ_INFO-- updated as per AlexW's suggestion,
defined 1 new flag and
2014 Jul 09
5
[LLVMdev] [PATCH][REQUEST] Could someone submit this CSR Kalimba definitions patch please?
Hello LLVMdev!!
Yesterday I posted a patch request to the llvm-commits list requesting
that someone could apply a patch to Triple.h and Triple.cpp for me. I
didn't get any response so I wondered whether I should have posted to
this list instead.
My story is as follows: we are trying to get lldb/llvm support for CSRs
range of Kalimba DSPs. Eventually we are planning to hire someone to
2017 Jul 18
2
CentOS for PowerPC Board ( Freescale T2080) with U-Boot
Hello,
I got CentOS for PPC64 from this link
<http://mirror.centos.org/altarch/7/isos/ppc64/> but it uses grub. I want
to use CentOS on a PowerPC Freescale T2080 board with U-Boot as the boot
loader. Is it available?
Thanks and regards
Jaytirth S. Khairatkar | Assistant Manager
--------------------------------------------------------------------------
--------------------------
2024 Jul 29
1
[PATCH 1/2] [v2] drm/nouveau: retain device pointer in nvkm_gsp_mem object
On Mon, 2024-07-29 at 18:07 -0500, Timur Tabi wrote:
Store the struct device pointer used to allocate the DMA buffer in
the nvkm_gsp_mem object. This allows nvkm_gsp_mem_dtor() to release
the buffer without needing the nvkm_gsp. This is needed so that
we can retain DMA buffers even after the nvkm_gsp object is deleted.
Signed-off-by: Timur Tabi <ttabi at nvidia.com<mailto:ttabi at
2013 Mar 21
2
remote connection issue 'virsh -c qemu+ssh:///root@localhost/system list'
Hi,
I'm trying remote connection with qemu hypervisor on FSL PPC board.
The libvirt server is the PPC board.
root at ppc:~# ifconfig eth0 10.193.20.109
root at ppc:~# libvirtd -d
root at ppc:~# virsh -c qemu:///system define test.xml
root at ppc:~# virsh -c qemu:///system start test
root at ppc:~# virsh -c qemu:///system list --all
Id Name State
2014 Jun 12
2
Re: libguestfs supermin error
On Thu, Jun 12, 2014 at 05:08:37PM +0530, abhishek jain wrote:
> Hi Rich
>
> I have all the virtio modules available in the kernel but I'm getting the
> same result .
It doesn't appear to be using any kernel modules. I would have
expected to see output such as this:
supermin: internal insmod virtio.ko
It seems as if you might not be setting SUPERMIN_MODULES; or maybe you
2013 Dec 02
1
Xen on Freescale i.MX6Q
Greetings,
I''m interested in getting Xen to work on a Freescale i.MX6Q ARM7 based
board. I''m a little confused by the wiki. As I understand it, I''ll need to
use PV. However, its not clear to me whether this capability has been
folded into the current code base or whether I need to look at the older
code. I''m running Ubuntu 11.10. Thanks in advance for any
2024 Feb 14
1
[PATCH 1/2] drm/nouveau: don't fini scheduler if not initialized
On Fri, 2024-02-02 at 17:14 +0000, Timur Tabi wrote:
> On Fri, 2024-02-02 at 01:05 +0100, Danilo Krummrich wrote:
> > nouveau_abi16_ioctl_channel_alloc() and nouveau_cli_init() simply call
> > their corresponding *_fini() counterpart. This can lead to
> > nouveau_sched_fini() being called without struct nouveau_sched ever
> > being initialized in the first place.
>
2018 Sep 14
1
Suggestion: use mustWork = TRUE as the default for system.file
Hello all,
Currently, the default behavior for system.file() is to return "" for
faulty paths.
I've found this behavior to be difficult when debugging, since it passes
the empty path onto other functions. I initially wrote in errors myself
(with code like `if(path == "") stop(?Path not found?)`), but I now use
mustWork=TRUE or fs::path_package(), which errors by default.
2014 Oct 28
3
[LLVMdev] DragonEgg3.3 support for gcc cross compilers
No. The gcc cross compiler being used (tilera-gcc) is indeed 64-bit.
Thanks
On Tue, Oct 28, 2014 at 11:01 AM, Anton Korobeynikov <
anton at korobeynikov.info> wrote:
> Looks like your gcc is 32-bit and you're trying to load 64-bit plugin.
>
> On Tue, Oct 28, 2014 at 8:27 PM, Ajay Panyala <ajay.panyala at gmail.com>
> wrote:
> > Hi Brian,
> >
> >
2014 Oct 28
2
[LLVMdev] DragonEgg3.3 support for gcc cross compilers
I am using a gcc (v 4.8.2) cross compiler for the tilera architecture.
There is an LLVM (v 3.3) cross compiler available for tilera (
http://tilera.github.io/llvm),
but the frontend only has partial support for certain tilera intrinsics and
no OpenMP support.
Hence, I have decided to use DragonEgg (v 3.3) to resolve this. I was able
to build
DragonEgg, but when I pass the command line argument