Re: Linux on Hyper-V 1) cd006086fa5d ata_piix: defer disks to the Hyper-V drivers by default 2) db63a4c8115a libata: add a host flag to ignore detected ATA device FW: use hv_storvsc instead of ata_piix to handle the IDE disks devices ( but not for the ...

[Victor Miasnikov]

Hi!

> > > VVM > > > Hyper-V admins need _worked_ Linux v3.4.X / v3.3.X / v3.2.X
> > >I can help you with the ata patch on specific set of distros of interest.
> > >If the system that you are interested loads the ata_piix module,
> > >we can solve the issue on hand using modprobe rules rather than a patch
> > against the ata driver.
> >
> >  K.Y.:  Youre _theory_ ( about "can solve the issue on hand using modprobe
> > rules") is wrong for:

> As I said,  if the ata_piix driver is a loadable module, 
> we can solve the issue with modprobe rules. 
> If it is not a loadable module we cannot obviously 
> solve the problem with modprobe rules
> and we will need the ata patch.

Nothing new: 
  -- "the ata patch" is need, if we want worked 100% / 100% Linux on Hyper-V
  -- "solve the problem with modprobe rules" very often not worked solution (  i.e. if the ata_piix driver  . . . )

Total: 

{
 cd006086fa5d ata_piix: defer disks to the Hyper-V drivers by default

and its prerequisite

 db63a4c8115a libata: add a host flag to ignore detected ATA devices
}
need be backported from

3.5 

to

3.4.latest
3.3.latest
3.2.latest



Best regards, Victor Miasnikov
Blog:  http://vvm.blog.tut.by/ 

P.S.

> As I said,  if the ata_piix driver is a loadable module, 
> we can solve the issue with modprobe rules. 

We can test Youre theory:

----- Original Message ----- 
From: "Victor Miasnikov"
To: "KY Srinivasan"
Sent: Monday, June 04, 2012 6:50 PM

 . . .

with use only  "modprobe rules" prepare binary patch ( .xDelta)  for <Linux_Distib_ZZZZ_Kernel_3.2_>

  . . .

Goal: work in Hyper-V guest as ( ( Linux_Distib_ZZZZ_Kernel_3.1_.iso ) + worked mouse ) ) in LiveCD and after install

--


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/