Devices breaking due to CONFIG_ZONE_DEVICE
Hi All,
Commit 033fbae988fc ("mm: ZONE_DEVICE for "device memory"") has introduced CONFIG_ZONE_DEVICE while sacrificing CONFIG_ZONE_DMA. Distributions like Ubuntu has started enabling CONFIG_ZONE_DEVICE and thus breaking parallel port. Please have a look at
https://bugzilla.kernel.org/show_bug.cgi?id=110931 for the bug report.
Apart from parallel port I can see some sound drivers will also break.
Now what is the possible solution for this?
Regards
Sudip
Quoted 10 lines · Sudip Mukherjee
Hi All,
Commit033fbae988fc("mm:ZONE_DEVICEfor "device memory"") has introducedCONFIG_ZONE_DEVICEwhile sacrificingCONFIG_ZONE_DMA. Distributions like Ubuntu has started enablingCONFIG_ZONE_DEVICEand thus breaking parallel port. Please have a look at
https://bugzilla.kernel.org/show_bug.cgi?id=110931 for the bug report.Apart from parallel port I can see some sound drivers will also break.
Now what is the possible solution for this?
The tradeoff here is enabling direct-I/O for persistent memory vs support for legacy devices.
One possible solution is to alias ZONE_DMA and ZONE_DEVICE. At early boot if pmem is detected disable these legacy devices, or the reverse disable DMA to persistent memory if a legacy device is detected. The latter is a bit harder to do as I think we would want to make the decision early during memory init before we would know if any parallel ports or ISA sound cards are present.
Quoted 16 lines · Dan Williams
Quoted 10 lines · Sudip Mukherjee
Hi All,
Commit033fbae988fc("mm:ZONE_DEVICEfor "device memory"") has introducedCONFIG_ZONE_DEVICEwhile sacrificingCONFIG_ZONE_DMA. Distributions like Ubuntu has started enablingCONFIG_ZONE_DEVICEand thus breaking parallel port. Please have a look at
https://bugzilla.kernel.org/show_bug.cgi?id=110931 for the bug report.Apart from parallel port I can see some sound drivers will also break.
Now what is the possible solution for this?
The tradeoff here is enabling direct-I/O for persistent memory vs support for legacy devices.
Quoted 6 lines
One possible solution is to alias
ZONE_DMAandZONE_DEVICE. At early boot if pmem is detected disable these legacy devices, or the reverse disable DMA to persistent memory if a legacy device is detected. The latter is a bit harder to do as I think we would want to make the decision early during memory init before we would know if any parallel ports or ISA sound cards are present.
...another option that might be cleaner is to teach GFP_DMA to get memory from a different mechanism. I.e. don't use the mm-zone infrastructure to organize that small 16MB pool of memory.
+ linux-mm
Quoted 27 lines · Dan Williams
Quoted 16 lines · Dan Williams
Quoted 10 lines · Sudip Mukherjee
Hi All,
Commit033fbae988fc("mm:ZONE_DEVICEfor "device memory"") has introducedCONFIG_ZONE_DEVICEwhile sacrificingCONFIG_ZONE_DMA. Distributions like Ubuntu has started enablingCONFIG_ZONE_DEVICEand thus breaking parallel port. Please have a look at
https://bugzilla.kernel.org/show_bug.cgi?id=110931 for the bug report.Apart from parallel port I can see some sound drivers will also break.
Now what is the possible solution for this?
The tradeoff here is enabling direct-I/O for persistent memory vs support for legacy devices.
Quoted 6 lines
One possible solution is to alias
ZONE_DMAandZONE_DEVICE. At early boot if pmem is detected disable these legacy devices, or the reverse disable DMA to persistent memory if a legacy device is detected. The latter is a bit harder to do as I think we would want to make the decision early during memory init before we would know if any parallel ports or ISA sound cards are present....another option that might be cleaner is to teach
GFP_DMAto get memory from a different mechanism. I.e. don't use the mm-zone infrastructure to organize that small 16MB pool of memory.
Signature · 11 lines
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix ImendA?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG NA 1/4 rnberg)
--
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>