search for: drvier

...amiliar with the xen code. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org   Ah, I forgot to add libvirt-users in Cc... sorry.  The thing I found today is that if libvirt uses xend driver, shutdown events are delivered, but if libvirt uses libxl drvier, doesn't show up anything. It seems there are bugs on shutdown event, so I did dig into the libvirt source briefly, but I couldn't find where libxl driver calls event callback. Any help will be greatly appreciated. Especially someone who is familiar with xen code.

Cole Robinson wrote: > On 02/18/2014 05:12 AM, Kim Larry wrote: > >> The thing I found today is that if libvirt uses xend driver, shutdown events >> are delivered, but if libvirt uses libxl drvier, doesn't show up anything. It >> seems there are bugs on shutdown event, so I did dig into the libvirt source >> briefly, but I couldn't find where libxl driver calls event callback. >> >> Any help will be greatly appreciated. Especially someone who is familiar with...

...RedHat4.5 , the NIC can not be found. As I type the command "lspci" in RHEL4.5 domU, it returned: pcilib: Cannot open /proc/bus/pci lspci: Cannot find any working access method. And I found the three lines in "dmesg" output: XENBUS: Device with no drvier: device/vbd/51713 XENBUS: Device with no driver: device/pci/0 XENBUS: Device with no driver: device/vif/0 After that, I tried to rebuild redhat4.5''s kernel, and set: CONFIG_PCI=y CONFIG_XEN_PCIDEV_FRONTEND=y in the config file "kernel-2.6.9-i686-...

...rote: > >> Cole Robinson wrote: >> >>> On 02/18/2014 05:12 AM, Kim Larry wrote: >>> >>> >>>> The thing I found today is that if libvirt uses xend driver, shutdown events >>>> are delivered, but if libvirt uses libxl drvier, doesn't show up anything. It >>>> seems there are bugs on shutdown event, so I did dig into the libvirt source >>>> briefly, but I couldn't find where libxl driver calls event callback. >>>> >>>> Any help will be greatly appreciated. Especial...

...we >> don't even attempt isolate_movable_page()? > > For now, we shouldn't have such a false positive because PageMovable > checks page->_mapcount == PAGE_MOVABLE_MAPCOUNT_VALUE as well as PG_movable > under PG_lock. > > But I read your question about user-mapped drvier pages so we cannot > use _mapcount anymore so I will find another thing. A option is this. > > static inline int PageMovable(struct page *page) > { > int ret = 0; > struct address_space *mapping; > struct address_space_operations *a_op; > >...

...we >> don't even attempt isolate_movable_page()? > > For now, we shouldn't have such a false positive because PageMovable > checks page->_mapcount == PAGE_MOVABLE_MAPCOUNT_VALUE as well as PG_movable > under PG_lock. > > But I read your question about user-mapped drvier pages so we cannot > use _mapcount anymore so I will find another thing. A option is this. > > static inline int PageMovable(struct page *page) > { > int ret = 0; > struct address_space *mapping; > struct address_space_operations *a_op; > >...

....c index ff6562f602e0..de211ef3738c 100644 --- a/drivers/vdpa/vdpa.c +++ b/drivers/vdpa/vdpa.c @@ -63,7 +63,7 @@ static void vdpa_release_dev(struct device *d) * @config: the bus operations that is supported by this device * @size: size of the parent structure that contains private data * - * Drvier should use vdap_alloc_device() wrapper macro instead of + * Driver should use vdpa_alloc_device() wrapper macro instead of * using this directly. * * Returns an error when parent/config/dma_dev is not set or fail to get -- 2.20.1

...rs. The request may even be replicated there. > > So it is really hard to find the right request queue to put > > the request into and sort them on the queue. > > Hmm.., I thought that all the incoming requests to dm/md driver will > remain in a single queue maintained by that drvier (irrespective of the > fact in which request queue these requests go in lower layers after > replication or other operation). I am not very familiar with dm/md > implementation. I will read more about it.... They never look into the queues maintained in drivers. Some of them have its own...

Hi, As of now I have been using xVM on Solaris 11 Express b151a. And I am looking for PV Driver for Windows 2008 and Windows 2008R2. So which open source PV driver can I use for these OSs? And I feel the the performance of PV drvier on Windows 2003 I downloaded from Sun site, this is early driver, is bad. The network performance is usually 20kbp/s. So I want to know how I can get better performance. Thanks Ryo

...rs. The request may even be replicated there. > > So it is really hard to find the right request queue to put > > the request into and sort them on the queue. > > Hmm.., I thought that all the incoming requests to dm/md driver will > remain in a single queue maintained by that drvier (irrespective of the > fact in which request queue these requests go in lower layers after > replication or other operation). I am not very familiar with dm/md > implementation. I will read more about it.... They never look into the queues maintained in drivers. Some of them have its own...

...esn't have that much buffer. what is there now should work on more systems, and also should be more robust to underruns. - got rid of the NONBLOCK flag. The code was only half-way geared to nonblocking mode, resulting in very high cpu load with the alsa driver (more than 2x the oss drvier). Getting rid of the flag fixed the problem. Other apps seems to use this mode by default as well. - made minor changes to track latest alsa cvs code. It seems to be working quite well on my system here, but I do notice that mono files are getting spit out of only my left channel, instead of...

...ake eblake redhat com +1-919-301-3266 >> Libvirt virtualization library http://libvirt.org > > > Ah, I forgot to add libvirt-users in Cc... sorry. > > The thing I found today is that if libvirt uses xend driver, shutdown events > are delivered, but if libvirt uses libxl drvier, doesn't show up anything. It > seems there are bugs on shutdown event, so I did dig into the libvirt source > briefly, but I couldn't find where libxl driver calls event callback. > > Any help will be greatly appreciated. Especially someone who is familiar with > xen code....

On 02/18/2014 10:45 PM, Jim Fehlig wrote: > Cole Robinson wrote: >> On 02/18/2014 05:12 AM, Kim Larry wrote: >> >>> The thing I found today is that if libvirt uses xend driver, shutdown events >>> are delivered, but if libvirt uses libxl drvier, doesn't show up anything. It >>> seems there are bugs on shutdown event, so I did dig into the libvirt source >>> briefly, but I couldn't find where libxl driver calls event callback. >>> >>> Any help will be greatly appreciated. Especially someone who i...

I can't get it to run since v1.1 (lossywav) with latest dev wine or the stable builds. Last version of lossywav wich worked was 1.0. My PC : Piii-550, mga400 vga, intel bx chipset, 512mb, debian lenny/sid 2.6.18, wine 1.13 Here is the crash log: @p550:~/tmp$ wine lossywav fixme:ntoskrnl:KeInitializeSpinLock stub: 0x4577a4 wine: Unhandled exception 0x0eedfade at address 0x0000:0x7b845c60

...nce cd and enter linux dd at the prompt. I load the driver in the install and it still fails to find any disks. I have looked at the virtual consoles after the module disk and I see some strange information: failed to open /tmp/drivers/modules.pcimap: no such file or directory failed to open /tmp/drviers/pci.ids: no such file or directory ..... modules to insert mptbase mptscsih mptsas module(s) mptbase mptscsih mptsas not found So the driver disk is loading but....it can't find the modules. So I went on looking at the driver disk and found: -rw-r--r-- 1 root root 48 Dec 20 2005 disk-...

Might have been better as a separate migration patch and then a compaction patch. It's prefixed mm/compaction, but most changed are in mm/migrate.c On 03/30/2016 09:12 AM, Minchan Kim wrote: > We have allowed migration for only LRU pages until now and it was > enough to make high-order pages. But recently, embedded system(e.g., > webOS, android) uses lots of non-movable pages(e.g.,

Might have been better as a separate migration patch and then a compaction patch. It's prefixed mm/compaction, but most changed are in mm/migrate.c On 03/30/2016 09:12 AM, Minchan Kim wrote: > We have allowed migration for only LRU pages until now and it was > enough to make high-order pages. But recently, embedded system(e.g., > webOS, android) uses lots of non-movable pages(e.g.,

...aces) implying PageLRU() so that we > don't even attempt isolate_movable_page()? For now, we shouldn't have such a false positive because PageMovable checks page->_mapcount == PAGE_MOVABLE_MAPCOUNT_VALUE as well as PG_movable under PG_lock. But I read your question about user-mapped drvier pages so we cannot use _mapcount anymore so I will find another thing. A option is this. static inline int PageMovable(struct page *page) { int ret = 0; struct address_space *mapping; struct address_space_operations *a_op; if (!test_bit(PG_movable, &(page->f...

Use struct msi_ops to hook PCI MSI operations, and use struct msi_irqs to refactor PCI MSI drvier. Signed-off-by: Yijing Wang <wangyijing at huawei.com> --- drivers/pci/msi.c | 351 ++++++++++++++++++++++++++++++--------------------- include/linux/msi.h | 14 +- include/linux/pci.h | 11 +- 3 files changed, 222 insertions(+), 154 deletions(-) diff --git a/drivers/pci/msi.c b/dri...

...g; linux-arch at vger.kernel.org; Basu > Arnab-B45036; virtualization at lists.linux-foundation.org; Hanjun Guo; Yijing Wang > Subject: [RFC PATCH 09/11] PCI/MSI: refactor PCI MSI driver > > Use struct msi_ops to hook PCI MSI operations, > and use struct msi_irqs to refactor PCI MSI drvier. > > Signed-off-by: Yijing Wang <wangyijing at huawei.com> > --- > drivers/pci/msi.c | 351 ++++++++++++++++++++++++++++++--------------------- > include/linux/msi.h | 14 +- > include/linux/pci.h | 11 +- > 3 files changed, 222 insertions(+), 154 deletions(-) &g...