linux.git/drivers/media, branch v4.4-rc2

various: fix pci_set_dma_mask return value checking

2015-11-21T00:17:32+00:00

pci_set_dma_mask returns a negative errno value, not a bool like
pci_dma_supported.  This of course was just a giant test for attention :)

Signed-off-by: Christoph Hellwig 
Reported-by: Jongman Heo 
Tested-by: Jongman Heo 	[pcnet32]
Acked-by: Mauro Carvalho Chehab 
Cc: Hans Verkuil 
Cc: Antti Palosaari 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

netup_unidvb: use pci_set_dma_mask insted of pci_dma_supported

2015-11-11T00:32:11+00:00

This ensures the dma mask that is supported by the driver is recorded
in the device structure.

Signed-off-by: Christoph Hellwig 
Cc: Sergey Kozlov 
Cc: Mauro Carvalho Chehab 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

cx23885: use pci_set_dma_mask insted of pci_dma_supported

2015-11-11T00:32:11+00:00

This ensures the dma mask that is supported by the driver is recorded
in the device structure.

Signed-off-by: Christoph Hellwig 
Cc: Mauro Carvalho Chehab 
Cc: Hans Verkuil 
Cc: Pawel Osciak 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

cx25821: use pci_set_dma_mask insted of pci_dma_supported

2015-11-11T00:32:11+00:00

This ensures the dma mask that is supported by the driver is recorded
in the device structure.

Signed-off-by: Christoph Hellwig 
Cc: Mauro Carvalho Chehab 
Cc: Hans Verkuil 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

cx88: use pci_set_dma_mask insted of pci_dma_supported

2015-11-11T00:32:11+00:00

This ensures the dma mask that is supported by the driver is recorded
in the device structure.

Signed-off-by: Christoph Hellwig 
Cc: Mauro Carvalho Chehab 
Cc: Hans Verkuil 
Cc: Sakari Ailus 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

saa7134: use pci_set_dma_mask insted of pci_dma_supported

2015-11-11T00:32:11+00:00

This ensures the dma mask that is supported by the driver is recorded
in the device structure.

Signed-off-by: Christoph Hellwig 
Cc: Mauro Carvalho Chehab 
Cc: Pawel Osciak 
Cc: Hans Verkuil 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

saa7164: use pci_set_dma_mask insted of pci_dma_supported

2015-11-11T00:32:11+00:00

This ensures the dma mask that is supported by the driver is recorded
in the device structure.

Signed-off-by: Christoph Hellwig 
Cc: Mauro Carvalho Chehab 
Cc: Hans Verkuil 
Cc: Steven Toth 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

tw68-core: use pci_set_dma_mask insted of pci_dma_supported

2015-11-11T00:32:11+00:00

This ensures the dma mask that is supported by the driver is recorded
in the device structure.

Signed-off-by: Christoph Hellwig 
Cc: Hans Verkuil 
Cc: Mauro Carvalho Chehab 
Cc: Pawel Osciak 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

remove abs64()

2015-11-09T23:11:24+00:00

Switch everything to the new and more capable implementation of abs().
Mainly to give the new abs() a bit of a workout.

Cc: Michal Nazarewicz 
Cc: John Stultz 
Cc: Ingo Molnar 
Cc: Steven Rostedt 
Cc: Peter Zijlstra 
Cc: Masami Hiramatsu 
Cc: Peter Zijlstra 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

mm, page_alloc: distinguish between being unable to sleep, unwilling to sleep and avoiding waking kswapd

2015-11-07T01:50:42+00:00

__GFP_WAIT has been used to identify atomic context in callers that hold
spinlocks or are in interrupts.  They are expected to be high priority and
have access one of two watermarks lower than "min" which can be referred
to as the "atomic reserve".  __GFP_HIGH users get access to the first
lower watermark and can be called the "high priority reserve".

Over time, callers had a requirement to not block when fallback options
were available.  Some have abused __GFP_WAIT leading to a situation where
an optimisitic allocation with a fallback option can access atomic
reserves.

This patch uses __GFP_ATOMIC to identify callers that are truely atomic,
cannot sleep and have no alternative.  High priority users continue to use
__GFP_HIGH.  __GFP_DIRECT_RECLAIM identifies callers that can sleep and
are willing to enter direct reclaim.  __GFP_KSWAPD_RECLAIM to identify
callers that want to wake kswapd for background reclaim.  __GFP_WAIT is
redefined as a caller that is willing to enter direct reclaim and wake
kswapd for background reclaim.

This patch then converts a number of sites

o __GFP_ATOMIC is used by callers that are high priority and have memory
  pools for those requests. GFP_ATOMIC uses this flag.

o Callers that have a limited mempool to guarantee forward progress clear
  __GFP_DIRECT_RECLAIM but keep __GFP_KSWAPD_RECLAIM. bio allocations fall
  into this category where kswapd will still be woken but atomic reserves
  are not used as there is a one-entry mempool to guarantee progress.

o Callers that are checking if they are non-blocking should use the
  helper gfpflags_allow_blocking() where possible. This is because
  checking for __GFP_WAIT as was done historically now can trigger false
  positives. Some exceptions like dm-crypt.c exist where the code intent
  is clearer if __GFP_DIRECT_RECLAIM is used instead of the helper due to
  flag manipulations.

o Callers that built their own GFP flags instead of starting with GFP_KERNEL
  and friends now also need to specify __GFP_KSWAPD_RECLAIM.

The first key hazard to watch out for is callers that removed __GFP_WAIT
and was depending on access to atomic reserves for inconspicuous reasons.
In some cases it may be appropriate for them to use __GFP_HIGH.

The second key hazard is callers that assembled their own combination of
GFP flags instead of starting with something like GFP_KERNEL.  They may
now wish to specify __GFP_KSWAPD_RECLAIM.  It's almost certainly harmless
if it's missed in most cases as other activity will wake kswapd.

Signed-off-by: Mel Gorman 
Acked-by: Vlastimil Babka 
Acked-by: Michal Hocko 
Acked-by: Johannes Weiner 
Cc: Christoph Lameter 
Cc: David Rientjes 
Cc: Vitaly Wool 
Cc: Rik van Riel 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds