similar to: [PATCH 1/4] pvSCSI : Add white list to SCSI command emulation

pvSCSI backend driver Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com> Signed-off-by: Jun Kamada <kama@jp.fujitsu.com> ----- Jun Kamada _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

This is a resend of a previously sent patch-set. This patch-set deals with some of the style isues in blkvsc_drv.c. We also get rid most of the "dead code" in this file: 1) Get rid of most of the forward declarations in this file. The only remaining forward declarations are to deal with circular dependencies. 2) Get rid of most of the dead code in the file. Some of the

This is a resend of a previously sent patch-set. This patch-set deals with some of the style isues in blkvsc_drv.c. We also get rid most of the "dead code" in this file: 1) Get rid of most of the forward declarations in this file. The only remaining forward declarations are to deal with circular dependencies. 2) Get rid of most of the dead code in the file. Some of the

More cleanup. In this patch-set we deal with the following issues: 1) While a Linux guest on Hyper-V can be assigned removable media devices (DVD, floppy etc), these devices are not handled by the Hyper-V block driver. So, we cleanup all the dead code dealing with removable media devices. 2) There were multiple functions to retrieve information about the device. Since much of

More cleanup. In this patch-set we deal with the following issues: 1) While a Linux guest on Hyper-V can be assigned removable media devices (DVD, floppy etc), these devices are not handled by the Hyper-V block driver. So, we cleanup all the dead code dealing with removable media devices. 2) There were multiple functions to retrieve information about the device. Since much of

This patch-set deals with some of the style isues in blkvsc_drv.c. We also get rid most of the "dead code" in this file: 1) Get rid of most of the forward declarations in this file. The only remaining forward declarations are to deal with circular dependencies. 2) Get rid of most of the dead code in the file. Some of the functions in this file are place holders - they

This patch-set deals with some of the style isues in blkvsc_drv.c. We also get rid most of the "dead code" in this file: 1) Get rid of most of the forward declarations in this file. The only remaining forward declarations are to deal with circular dependencies. 2) Get rid of most of the dead code in the file. Some of the functions in this file are place holders - they

The latest upstream merge changed struct block_device_operations: This merge got rid of blkvsc_media_changed and introduced the function blkvsc_check_events. This broke all the patches that were sent after the tree was closed the last time. This is a resend of this patch-set to account for this change in the kernel. More cleanup. In this patch-set we deal with the following issues: 1) While a

The latest upstream merge changed struct block_device_operations: This merge got rid of blkvsc_media_changed and introduced the function blkvsc_check_events. This broke all the patches that were sent after the tree was closed the last time. This is a resend of this patch-set to account for this change in the kernel. More cleanup. In this patch-set we deal with the following issues: 1) While a

I''m trying to compile pvscsi out-of-tree, and I''m getting an error that set_phys_to_machine is not defined when I try to load the module (with the warning to that effect at compile time too). This used to work fine in pvops. It seems that netfront uses that symbol in a module so I''m confused as to why pvscsi can''t... any suggestions? Is it one of the virtues of

If you have any of the devices listed below, please test with a recent -stable or -current. They will stop working in 4.9 and 5.2 although old behavior can _temporarily_ be enabled by adding "options DA_OLD_QUIRKS" to your kernel config. If I don't hear from anyone, they'll be going away permanently after the releases. -Nate #ifdef DA_OLD_QUIRKS /* Below a list of

I'm seeing this sometimes before my machine dies: Oct 26 03:28:00 belle kernel: acd0: WARNING - READ_TOC taskqueue timeout - completing request directly Oct 26 03:28:00 belle kernel: acd0: WARNING - READ_TOC freeing taskqueue zombie request Oct 26 03:30:00 belle kernel: acd0: WARNING - READ_TOC taskqueue timeout - completing request directly Oct 26 03:30:00 belle kernel: acd0: WARNING -

Hi everyone, I''ve been running a zfs fileserver for about a month now (on snv_91) and it''s all working really well. I''m scrubbing once a week and nothing has come up as a problem yet. I''m a little worried as I''ve just noticed these messages in /var/adm/message and I don''t know if they''re bad or just informational: Aug 2 14:46:06

Under the assumption that in these cases recurring faults aren''t a security issue and it can be expected that the drivers there are going to try to take care of the problem. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/drivers/passthrough/amd/iommu_init.c +++ b/xen/drivers/passthrough/amd/iommu_init.c @@ -625,6 +625,18 @@ static void parse_event_log_entry(struct

Forgot to copy the virtualization list.. On Wed, 2009-09-30 at 11:53 -0700, Alok Kataria wrote: > Hi James, > > Given that their are no more modification requests, I think this driver > should be ready for prime time now. I have incorporated the remaining > few outstanding comments while rebasing the patch for 32-rc1. > > Please consider this for the SCSI tree. Also let me

Forgot to copy the virtualization list.. On Wed, 2009-09-30 at 11:53 -0700, Alok Kataria wrote: > Hi James, > > Given that their are no more modification requests, I think this driver > should be ready for prime time now. I have incorporated the remaining > few outstanding comments while rebasing the patch for 32-rc1. > > Please consider this for the SCSI tree. Also let me

Here is the V6, which addresses most of the suggestions from Chris'. Please consider this for the scsi-tree. Thanks, Alok (Hoping Sixth time's a charm :) VMware PVSCSI driver - v6. Changelog (v6-v5) - remove unneeded header file includes. - make pvscsi_dev as a static function. - IRQF_SHARED only for INT/X, pass zero for rest. - use __get_free_pages to allocate ctx->sgl.

Here is the V6, which addresses most of the suggestions from Chris'. Please consider this for the scsi-tree. Thanks, Alok (Hoping Sixth time's a charm :) VMware PVSCSI driver - v6. Changelog (v6-v5) - remove unneeded header file includes. - make pvscsi_dev as a static function. - IRQF_SHARED only for INT/X, pass zero for rest. - use __get_free_pages to allocate ctx->sgl.

> On 21 May 2005, at 08:53, James Harper wrote: > > We''re going to rip the fixed ticker out of Xen and allow domains to > specify a background ticker at a rate of their choice, which ought to > fix this for you. So I could have a domain with 100HZ, and another with 1000HZ? That would be nice. > Of course, you''re pretty screwed running this kind of > thing

On Wed, Sep 11, 2019 at 03:28:27PM -0700, Ralph Campbell wrote: > Allow hmm_range_fault() to return success (0) when the CPU pagetable > entry points to the special shared zero page. > The caller can then handle the zero page by possibly clearing device > private memory instead of DMAing a zero page. > > Signed-off-by: Ralph Campbell <rcampbell at nvidia.com> > Cc: