[+Hugh Dickins]
Cheers,
Jia
On 5/4/2018 11:11 AM, Jia He Wrote:
In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by PAGE_SIZE
unaligned for rmap_item->address under memory pressure tests(start 20 guests
and run memhog in the host).
[+Hugh Dickins]
Cheers,
Jia
On 5/4/2018 11:11 AM, Jia He Wrote:
In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by PAGE_SIZE
unaligned for rmap_item->address under memory pressure tests(start 20 guests
and run memhog in the host).
Hi Hans,
One comment below, which I missed in review before.
On 29 April 2018 at 11:35, Hans de Goede wrote:
> Just like with PCI options ROMs, which we save in the setup_efi_pci*
> functions from arch/x86/boot/compressed/eboot.c, the EFI code / ROM itself
> sometimes may
Hi Hans,
One comment below, which I missed in review before.
On 29 April 2018 at 11:35, Hans de Goede wrote:
> Just like with PCI options ROMs, which we save in the setup_efi_pci*
> functions from arch/x86/boot/compressed/eboot.c, the EFI code / ROM itself
> sometimes may contain data which is
On 5/4/2018 3:12 AM, Andrew Morton wrote:
On Tue, 17 Apr 2018 16:13:48 +0530 Chintan Pandya
wrote:
Client can call vunmap with some intermediate 'addr'
which may not be the start of the VM area. Entire
unmap code works with vm->vm_start which is proper
but debug
On 5/4/2018 3:12 AM, Andrew Morton wrote:
On Tue, 17 Apr 2018 16:13:48 +0530 Chintan Pandya
wrote:
Client can call vunmap with some intermediate 'addr'
which may not be the start of the VM area. Entire
unmap code works with vm->vm_start which is proper
but debug object API is called with
On 4 May 2018 at 01:29, Luis R. Rodriguez wrote:
> On Sun, Apr 29, 2018 at 11:35:55AM +0200, Hans de Goede wrote:
[...]
>> diff --git a/Documentation/driver-api/firmware/request_firmware.rst
>> b/Documentation/driver-api/firmware/request_firmware.rst
>> index
On 4 May 2018 at 01:29, Luis R. Rodriguez wrote:
> On Sun, Apr 29, 2018 at 11:35:55AM +0200, Hans de Goede wrote:
[...]
>> diff --git a/Documentation/driver-api/firmware/request_firmware.rst
>> b/Documentation/driver-api/firmware/request_firmware.rst
>> index c8bddbdcfd10..560dfed76e38 100644
>>
From: Honghui Zhang
Using irq_chip solution to setup IRQs in order to consist
with IRQ framework.
Signed-off-by: Honghui Zhang
Acked-by: Ryder Lee
---
drivers/pci/host/pcie-mediatek.c | 206
From: Honghui Zhang
Two fixups for mediatek's host bridge:
The first patch fixup class type and vendor ID for MT7622.
The second patch fixup the IRQ handle routine by using irq_chip solution
to avoid IRQ reentry which may exist for both MT2712 and MT7622.
Change
From: Honghui Zhang
Using irq_chip solution to setup IRQs in order to consist
with IRQ framework.
Signed-off-by: Honghui Zhang
Acked-by: Ryder Lee
---
drivers/pci/host/pcie-mediatek.c | 206 ++-
1 file changed, 115 insertions(+), 91 deletions(-)
diff
From: Honghui Zhang
Two fixups for mediatek's host bridge:
The first patch fixup class type and vendor ID for MT7622.
The second patch fixup the IRQ handle routine by using irq_chip solution
to avoid IRQ reentry which may exist for both MT2712 and MT7622.
Change since v6:
- Remove the
From: Honghui Zhang
MT7622's hardware default value of vendor ID and class type is not correct,
fix that by setup the correct values before linkup with Endpoint.
Signed-off-by: Honghui Zhang
Acked-by: Ryder Lee
From: Honghui Zhang
MT7622's hardware default value of vendor ID and class type is not correct,
fix that by setup the correct values before linkup with Endpoint.
Signed-off-by: Honghui Zhang
Acked-by: Ryder Lee
---
drivers/pci/host/pcie-mediatek.c | 30 +++---
On Fri, Apr 27, 2018 at 5:19 PM, Dmitry Vyukov wrote:
> On Fri, Apr 27, 2018 at 7:30 AM, syzbot
> wrote:
>> Hello,
>>
>> syzbot hit the following crash on bpf-next commit
>> 5d1365940a68dd57b031b6e3c07d7d451cd69daf (Thu
On Fri, Apr 27, 2018 at 5:19 PM, Dmitry Vyukov wrote:
> On Fri, Apr 27, 2018 at 7:30 AM, syzbot
> wrote:
>> Hello,
>>
>> syzbot hit the following crash on bpf-next commit
>> 5d1365940a68dd57b031b6e3c07d7d451cd69daf (Thu Apr 12 18:09:05 2018 +)
>> Merge
On Fri, 04 May 2018 15:16:37 +1000
Michael Ellerman wrote:
> Nicholas Piggin writes:
>
> > Use the more refined and tested event polling loop from opal_put_chars
> > as the fallback console flush in the opal-kmsg path. This loop is used
> > by the
On Fri, 04 May 2018 15:16:37 +1000
Michael Ellerman wrote:
> Nicholas Piggin writes:
>
> > Use the more refined and tested event polling loop from opal_put_chars
> > as the fallback console flush in the opal-kmsg path. This loop is used
> > by the console driver today, whereas the opal-kmsg
On Fri, May 4, 2018 at 7:30 AM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:03f5781be2c7 bpf, x86_32: add eBPF JIT compiler for ia32
> git tree: bpf-next
> console output:
On Fri, May 4, 2018 at 7:30 AM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:03f5781be2c7 bpf, x86_32: add eBPF JIT compiler for ia32
> git tree: bpf-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1362723780
> kernel config:
On Fri, May 4, 2018 at 12:27 AM, Dan Carpenter wrote:
> There is no security problem here. The user is allowed to choose either
> v1 or v3. Using a double read race condition to choose v1 is not
> going to cause problems. It's slightly more complicated than just
>
On Fri, May 4, 2018 at 12:27 AM, Dan Carpenter wrote:
> There is no security problem here. The user is allowed to choose either
> v1 or v3. Using a double read race condition to choose v1 is not
> going to cause problems. It's slightly more complicated than just
> choosing it directly but that
Hello,
syzbot found the following crash on:
HEAD commit:03f5781be2c7 bpf, x86_32: add eBPF JIT compiler for ia32
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1362723780
kernel config: https://syzkaller.appspot.com/x/.config?x=3d356c2d908b7293
Hello,
syzbot found the following crash on:
HEAD commit:03f5781be2c7 bpf, x86_32: add eBPF JIT compiler for ia32
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1362723780
kernel config: https://syzkaller.appspot.com/x/.config?x=3d356c2d908b7293
On Fri, May 4, 2018 at 12:04 AM, Peter Rosin wrote:
> On 2018-05-04 06:08, Wenwen Wang wrote:
>> On Thu, May 3, 2018 at 3:34 PM, Peter Rosin wrote:
>>> On 2018-05-03 00:36, Wenwen Wang wrote:
In i2c_smbus_xfer_emulated(), there are two buffers: msgbuf0 and
On Fri, May 4, 2018 at 12:04 AM, Peter Rosin wrote:
> On 2018-05-04 06:08, Wenwen Wang wrote:
>> On Thu, May 3, 2018 at 3:34 PM, Peter Rosin wrote:
>>> On 2018-05-03 00:36, Wenwen Wang wrote:
In i2c_smbus_xfer_emulated(), there are two buffers: msgbuf0 and msgbuf1,
which are used to
There is no security problem here. The user is allowed to choose either
v1 or v3. Using a double read race condition to choose v1 is not
going to cause problems. It's slightly more complicated than just
choosing it directly but that doesn't make it a security issue.
It's a bit like typing with
There is no security problem here. The user is allowed to choose either
v1 or v3. Using a double read race condition to choose v1 is not
going to cause problems. It's slightly more complicated than just
choosing it directly but that doesn't make it a security issue.
It's a bit like typing with
Hi,
This includes several cleanup patches which aim to make the
code more concise and easier for reading. There aren't any
functionality changes.
Best regards,
Lu Baolu
Lu Baolu (4):
iommu: Clean up the comments for iommu_group_alloc
iommu/vt-d: Clean up unused variable in
Hi,
This includes several cleanup patches which aim to make the
code more concise and easier for reading. There aren't any
functionality changes.
Best regards,
Lu Baolu
Lu Baolu (4):
iommu: Clean up the comments for iommu_group_alloc
iommu/vt-d: Clean up unused variable in
Remove it to make the code more concise.
Signed-off-by: Lu Baolu
---
drivers/iommu/intel-iommu.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c
index 749d8f2..9064607 100644
---
Remove it to make the code more concise.
Signed-off-by: Lu Baolu
---
drivers/iommu/intel-iommu.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c
index 749d8f2..9064607 100644
--- a/drivers/iommu/intel-iommu.c
+++
Remove unnecessary parentheses to comply with preferred coding
style.
Signed-off-by: Lu Baolu
---
drivers/iommu/intel-svm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iommu/intel-svm.c b/drivers/iommu/intel-svm.c
index e8cd984..45f6e58
Remove unnecessary parentheses to comply with preferred coding
style.
Signed-off-by: Lu Baolu
---
drivers/iommu/intel-svm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iommu/intel-svm.c b/drivers/iommu/intel-svm.c
index e8cd984..45f6e58 100644
---
The pasid28 quirk is needed only for some pre-production devices.
Remove it to make the code concise.
Signed-off-by: Ashok Raj
Signed-off-by: Lu Baolu
---
drivers/iommu/intel-iommu.c | 32 ++--
The pasid28 quirk is needed only for some pre-production devices.
Remove it to make the code concise.
Signed-off-by: Ashok Raj
Signed-off-by: Lu Baolu
---
drivers/iommu/intel-iommu.c | 32 ++--
include/linux/intel-iommu.h | 1 -
2 files changed, 2 insertions(+), 31
@name parameter has been removed.
Signed-off-by: Lu Baolu
---
drivers/iommu/iommu.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
index d2aa2320..d87e7c2 100644
--- a/drivers/iommu/iommu.c
+++ b/drivers/iommu/iommu.c
@name parameter has been removed.
Signed-off-by: Lu Baolu
---
drivers/iommu/iommu.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
index d2aa2320..d87e7c2 100644
--- a/drivers/iommu/iommu.c
+++ b/drivers/iommu/iommu.c
@@ -322,7 +322,6 @@ static
Hi Andreas,
> Am 03.05.2018 um 20:50 schrieb Andreas Kemnade :
>
> On Thu, 3 May 2018 11:35:21 +0200
> H. Nikolaus Schaller wrote:
>
>
>> I have realized that the w2sg0004 is an exception (although a Sirf chip)
>> that it does not provide a WAKEUP
Hi Andreas,
> Am 03.05.2018 um 20:50 schrieb Andreas Kemnade :
>
> On Thu, 3 May 2018 11:35:21 +0200
> H. Nikolaus Schaller wrote:
>
>
>> I have realized that the w2sg0004 is an exception (although a Sirf chip)
>> that it does not provide a WAKEUP signal. And another significant
>> difference
Nicholas Piggin writes:
> Use the more refined and tested event polling loop from opal_put_chars
> as the fallback console flush in the opal-kmsg path. This loop is used
> by the console driver today, whereas the opal-kmsg fallback is not
> likely to have been used for years.
Nicholas Piggin writes:
> Use the more refined and tested event polling loop from opal_put_chars
> as the fallback console flush in the opal-kmsg path. This loop is used
> by the console driver today, whereas the opal-kmsg fallback is not
> likely to have been used for years.
>
> Use WARN_ONCE
Hello,
syzbot found the following crash on:
HEAD commit:c15f6d8d4715 Merge tag 'dma-mapping-4.17-4' of git://git.i..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=128d955b80
kernel config: https://syzkaller.appspot.com/x/.config?x=5a1dc06635c10d27
Hello,
syzbot found the following crash on:
HEAD commit:c15f6d8d4715 Merge tag 'dma-mapping-4.17-4' of git://git.i..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=128d955b80
kernel config: https://syzkaller.appspot.com/x/.config?x=5a1dc06635c10d27
On 2018-05-04 06:08, Wenwen Wang wrote:
> On Thu, May 3, 2018 at 3:34 PM, Peter Rosin wrote:
>> On 2018-05-03 00:36, Wenwen Wang wrote:
>>> In i2c_smbus_xfer_emulated(), there are two buffers: msgbuf0 and msgbuf1,
>>> which are used to save a series of messages, as mentioned in
On 2018-05-04 06:08, Wenwen Wang wrote:
> On Thu, May 3, 2018 at 3:34 PM, Peter Rosin wrote:
>> On 2018-05-03 00:36, Wenwen Wang wrote:
>>> In i2c_smbus_xfer_emulated(), there are two buffers: msgbuf0 and msgbuf1,
>>> which are used to save a series of messages, as mentioned in the comment.
>>>
Some code is dead because it is commented out.
Some is dead because it is uninteresting printks.
Some is dead because it declares unused functions.
Remove it all.
Signed-off-by: NeilBrown
---
drivers/staging/mt7621-pci/pci-mt7621.c | 14 --
1 file changed, 14
These resources are extracted from devicetree, so they aren't
needed here.
Signed-off-by: NeilBrown
---
drivers/staging/mt7621-pci/pci-mt7621.c | 19 ++-
1 file changed, 2 insertions(+), 17 deletions(-)
diff --git a/drivers/staging/mt7621-pci/pci-mt7621.c
These resources are extracted from devicetree, so they aren't
needed here.
Signed-off-by: NeilBrown
---
drivers/staging/mt7621-pci/pci-mt7621.c | 19 ++-
1 file changed, 2 insertions(+), 17 deletions(-)
diff --git a/drivers/staging/mt7621-pci/pci-mt7621.c
Some code is dead because it is commented out.
Some is dead because it is uninteresting printks.
Some is dead because it declares unused functions.
Remove it all.
Signed-off-by: NeilBrown
---
drivers/staging/mt7621-pci/pci-mt7621.c | 14 --
1 file changed, 14 deletions(-)
diff
This lock is never initialized, locked once, and never unlocked.
Clearly it is pointless - so remove it.
Signed-off-by: NeilBrown
---
drivers/staging/mt7621-spi/spi-mt7621.c |3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/staging/mt7621-spi/spi-mt7621.c
This lock is never initialized, locked once, and never unlocked.
Clearly it is pointless - so remove it.
Signed-off-by: NeilBrown
---
drivers/staging/mt7621-spi/spi-mt7621.c |3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/staging/mt7621-spi/spi-mt7621.c
mtk_phy_link_adjust takes a spinlock and disables
interrupts, but never unlocks.
This can leave interrupts disabled on one CPU and
various things stop working.
Signed-off-by: NeilBrown
---
drivers/staging/mt7621-eth/mdio.c |1 +
1 file changed, 1 insertion(+)
diff --git
Hi Roger,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17-rc3 next-20180503]
[cannot apply to xen-tip/linux-next]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url
As the Interrupts for the PCI adapters are listed in
devicetree we shouldn't need to have them explicit in the code.
The simplest way to do this is to use of_irq_parse_and_map_pci()
and specify an interrupt-map which identifies the different
PCI hosts by bus/slot numbers.
This has the advantage
mtk_phy_link_adjust takes a spinlock and disables
interrupts, but never unlocks.
This can leave interrupts disabled on one CPU and
various things stop working.
Signed-off-by: NeilBrown
---
drivers/staging/mt7621-eth/mdio.c |1 +
1 file changed, 1 insertion(+)
diff --git
Hi Roger,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17-rc3 next-20180503]
[cannot apply to xen-tip/linux-next]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url
As the Interrupts for the PCI adapters are listed in
devicetree we shouldn't need to have them explicit in the code.
The simplest way to do this is to use of_irq_parse_and_map_pci()
and specify an interrupt-map which identifies the different
PCI hosts by bus/slot numbers.
This has the advantage
The GNUBEE has 32MB flash, so set partitions accordingly.
Also remove "m25p,chunked-io" which isn't documented or
used anywhere (outside of freewrt).
Signed-off-by: NeilBrown
---
drivers/staging/mt7621-dts/gbpc1.dts |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
- remove white space at end of line.
- no more than 2 blank line at a time
- remove spaces before tabs
- use tabs to line things up
- re-indent some #define do{}while(0)
Signed-off-by: NeilBrown
---
drivers/staging/mt7621-pci/pci-mt7621.c | 291 +++
Hi all,
Changes since 20180503:
Non-merge commits (relative to Linus' tree): 3965
3776 files changed, 154371 insertions(+), 67944 deletions(-)
I have created today's linux-next tree at
git://git.kernel.org/pub/scm
The GNUBEE has 32MB flash, so set partitions accordingly.
Also remove "m25p,chunked-io" which isn't documented or
used anywhere (outside of freewrt).
Signed-off-by: NeilBrown
---
drivers/staging/mt7621-dts/gbpc1.dts |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
- remove white space at end of line.
- no more than 2 blank line at a time
- remove spaces before tabs
- use tabs to line things up
- re-indent some #define do{}while(0)
Signed-off-by: NeilBrown
---
drivers/staging/mt7621-pci/pci-mt7621.c | 291 +++
1 file changed,
Hi all,
Changes since 20180503:
Non-merge commits (relative to Linus' tree): 3965
3776 files changed, 154371 insertions(+), 67944 deletions(-)
I have created today's linux-next tree at
git://git.kernel.org/pub/scm
Code currently defines:
#define CONFIG_PCIE_PORT0
#define CONFIG_PCIE_PORT1
#define CONFIG_PCIE_PORT2
#define GPIO_PERST
and then compiles code only if they are defined.
We might want to disable some of these via devicetree one
day, but for now just remove the #defines and the
conditions - all
Code currently defines:
#define CONFIG_PCIE_PORT0
#define CONFIG_PCIE_PORT1
#define CONFIG_PCIE_PORT2
#define GPIO_PERST
and then compiles code only if they are defined.
We might want to disable some of these via devicetree one
day, but for now just remove the #defines and the
conditions - all
Highlights here are a bugfix for the ethernet driver,
and proper handling of irq assignments in the PCI driver.
We also make the full 32M of the gnubee flash available and start
cleaning up the mt7621-pci code.
---
NeilBrown (8):
staging: mt7621-eth: Lock is never unlocked.
staging:
Highlights here are a bugfix for the ethernet driver,
and proper handling of irq assignments in the PCI driver.
We also make the full 32M of the gnubee flash available and start
cleaning up the mt7621-pci code.
---
NeilBrown (8):
staging: mt7621-eth: Lock is never unlocked.
staging:
On Fri, May 4, 2018 at 1:11 AM, Eric W. Biederman wrote:
> Balbir Singh writes:
>
>> On Tue, 01 May 2018 12:35:16 -0500
>> ebied...@xmission.com (Eric W. Biederman) wrote:
>>
>>> Recently it was reported that mm_update_next_owner could get into
>>>
On Fri, May 4, 2018 at 1:11 AM, Eric W. Biederman wrote:
> Balbir Singh writes:
>
>> On Tue, 01 May 2018 12:35:16 -0500
>> ebied...@xmission.com (Eric W. Biederman) wrote:
>>
>>> Recently it was reported that mm_update_next_owner could get into
>>> cases where it was executing it's fallback
This patch introduces the support for VIRTIO_F_IO_BARRIER.
When this feature is negotiated, driver will use the barriers
suitable for hardware devices.
Signed-off-by: Tiwei Bie
---
This patch depends on below proposal for virtio-spec:
This patch introduces the support for VIRTIO_F_IO_BARRIER.
When this feature is negotiated, driver will use the barriers
suitable for hardware devices.
Signed-off-by: Tiwei Bie
---
This patch depends on below proposal for virtio-spec:
Hi Ravi,
I have some comments, please see below.
On Tue, 17 Apr 2018 10:02:41 +0530
Ravi Bangoria wrote:\
> diff --git a/include/linux/uprobes.h b/include/linux/uprobes.h
> index 7bd2760..2db3ed1 100644
> --- a/include/linux/uprobes.h
> +++
Hi Ravi,
I have some comments, please see below.
On Tue, 17 Apr 2018 10:02:41 +0530
Ravi Bangoria wrote:\
> diff --git a/include/linux/uprobes.h b/include/linux/uprobes.h
> index 7bd2760..2db3ed1 100644
> --- a/include/linux/uprobes.h
> +++ b/include/linux/uprobes.h
> @@ -122,6 +122,8 @@
On Wed, 2 May 2018 10:31:50 +0100
Jean-Philippe Brucker wrote:
> On 01/05/18 23:58, Jacob Pan wrote:
> Maybe this should be called "NG_PAGE_PASID",
> >>> Sure. I was thinking page range already implies non-global
> >>> pages.
> and "DOMAIN_PAGE"
On Wed, 2 May 2018 10:31:50 +0100
Jean-Philippe Brucker wrote:
> On 01/05/18 23:58, Jacob Pan wrote:
> Maybe this should be called "NG_PAGE_PASID",
> >>> Sure. I was thinking page range already implies non-global
> >>> pages.
> and "DOMAIN_PAGE" should
> instead be
On Thu, May 3, 2018 at 6:13 PM, Andy Shevchenko
wrote:
> Starting from the commit 0d0443288f22 the new function has been
> introduced which takes struct task_struct as a parameter. Though,
> compiler doesn't know where to get information about it at this stage.
On Thu, May 3, 2018 at 6:13 PM, Andy Shevchenko
wrote:
> Starting from the commit 0d0443288f22 the new function has been
> introduced which takes struct task_struct as a parameter. Though,
> compiler doesn't know where to get information about it at this stage.
>
> Add missed declaration of
On 5/3/2018 10:10 PM, Daniel Kurtz wrote:
On Thu, May 3, 2018 at 1:33 AM Mukunda,Vijendar
wrote:
On Thursday 03 May 2018 11:13 AM, Daniel Kurtz wrote:
Some checkpatch nits below...
On Tue, May 1, 2018 at 2:53 PM Vijendar Mukunda <
vijendar.muku...@amd.com>
On 5/3/2018 10:10 PM, Daniel Kurtz wrote:
On Thu, May 3, 2018 at 1:33 AM Mukunda,Vijendar
wrote:
On Thursday 03 May 2018 11:13 AM, Daniel Kurtz wrote:
Some checkpatch nits below...
On Tue, May 1, 2018 at 2:53 PM Vijendar Mukunda <
vijendar.muku...@amd.com>
wrote:
With in ACP, There
From: Joonsoo Kim
Currently, we use the zone index of preferred_zone which represents
the best matching zone for allocation, as classzone_idx. It has a problem
on NUMA system with ZONE_MOVABLE.
In NUMA system, it can be possible that each node has different populated
On Fri, May 4, 2018 at 12:04 AM, Greg KH wrote:
> On Thu, May 03, 2018 at 08:08:48PM +0530, Muni Sekhar wrote:
>> Hi All,
>>
>> I’m trying to understand how user mode buffer is written to low level
>> serial hardware registers.
>>
>> For this I read the kernel code and I came to
From: Joonsoo Kim
Currently, we use the zone index of preferred_zone which represents
the best matching zone for allocation, as classzone_idx. It has a problem
on NUMA system with ZONE_MOVABLE.
In NUMA system, it can be possible that each node has different populated
zones. For example, node 0
On Fri, May 4, 2018 at 12:04 AM, Greg KH wrote:
> On Thu, May 03, 2018 at 08:08:48PM +0530, Muni Sekhar wrote:
>> Hi All,
>>
>> I’m trying to understand how user mode buffer is written to low level
>> serial hardware registers.
>>
>> For this I read the kernel code and I came to know that from
Sorry for sending these twice, I made a formatting mistake in the
first series, and they would not apply properly. Hopefully these do
not show up as spam because of this.
I went through and fixed them all individually and re-committed them,
but kept the same commit messages. I still have a lot to
Sorry for sending these twice, I made a formatting mistake in the
first series, and they would not apply properly. Hopefully these do
not show up as spam because of this.
I went through and fixed them all individually and re-committed them,
but kept the same commit messages. I still have a lot to
On 05/03/2018 05:09 PM, TSUKADA Koutaro wrote:
> On 2018/05/03 11:33, Mike Kravetz wrote:
>> On 05/01/2018 11:54 PM, TSUKADA Koutaro wrote:
>>> On 2018/05/02 13:41, Mike Kravetz wrote:
What is the reason for not charging pages at allocation/reserve time? I am
not an expert in memcg
On 05/03/2018 05:09 PM, TSUKADA Koutaro wrote:
> On 2018/05/03 11:33, Mike Kravetz wrote:
>> On 05/01/2018 11:54 PM, TSUKADA Koutaro wrote:
>>> On 2018/05/02 13:41, Mike Kravetz wrote:
What is the reason for not charging pages at allocation/reserve time? I am
not an expert in memcg
This patch adds PCI quirk ID's for the Sound Blaster Z and Recon3Di.
Only the currently tested ID's have been added.
This patch also adds the ability to load alternative firmwares for each
card, the firmwares can be obtained from within the Windows driver.
The Recon3Di uses "ctefx-r3di.bin" and
This patch adds PCI quirk ID's for the Sound Blaster Z and Recon3Di.
Only the currently tested ID's have been added.
This patch also adds the ability to load alternative firmwares for each
card, the firmwares can be obtained from within the Windows driver.
The Recon3Di uses "ctefx-r3di.bin" and
This patch adds an unsolicited response tag for the front headphone
panel which uses the same hp_callback as the rear headphone detection.
This patch also adds pincfgs for the R3Di and SBZ which were taken from
the Windows driver. The pins are also defined in the function
ca0132_config. Both the
This patch adds an unsolicited response tag for the front headphone
panel which uses the same hp_callback as the rear headphone detection.
This patch also adds pincfgs for the R3Di and SBZ which were taken from
the Windows driver. The pins are also defined in the function
ca0132_config. Both the
This patch adds extra functions for shutdown on the Sound Blaster Z and
Recon3Di. The Recon3Di only has one specific functions, which sets the
GPIO data pins to 0 to prevent a popping noise.
The Sound Blaster Z exit sequence was taken from Windows. Without this
exit function, the card will not
This patch adds extra functions for shutdown on the Sound Blaster Z and
Recon3Di. The Recon3Di only has one specific functions, which sets the
GPIO data pins to 0 to prevent a popping noise.
The Sound Blaster Z exit sequence was taken from Windows. Without this
exit function, the card will not
Edit core functions to support the Sound Blaster Z and Recon3Di for
startup and loading of the DSP, as well as setting effects.
Signed-off-by: Connor McAdams
---
sound/pci/hda/patch_ca0132.c | 1070 --
1 file changed, 1018
Edit core functions to support the Sound Blaster Z and Recon3Di for
startup and loading of the DSP, as well as setting effects.
Signed-off-by: Connor McAdams
---
sound/pci/hda/patch_ca0132.c | 1070 --
1 file changed, 1018 insertions(+), 52 deletions(-)
Add functions ca0132_alt_select_out and ca0132_alt_select_in for
switching outputs and inputs for r3di and sbz. Also, add enumerated
controls for selecting output and input source.
Signed-off-by: Connor McAdams
---
sound/pci/hda/patch_ca0132.c | 597
Add functions ca0132_alt_select_out and ca0132_alt_select_in for
switching outputs and inputs for r3di and sbz. Also, add enumerated
controls for selecting output and input source.
Signed-off-by: Connor McAdams
---
sound/pci/hda/patch_ca0132.c | 597 +--
Add function to set vipsource on cards that use_alt_controls. Different
sequence. Also, add cvoice_switch_set at end of ca0132_select_in so that
when switching between inputs cvoice state is maintained.
Signed-off-by: Connor McAdams
---
sound/pci/hda/patch_ca0132.c | 71
Add function to set vipsource on cards that use_alt_controls. Different
sequence. Also, add cvoice_switch_set at end of ca0132_select_in so that
when switching between inputs cvoice state is maintained.
Signed-off-by: Connor McAdams
---
sound/pci/hda/patch_ca0132.c | 71
1 - 100 of 2134 matches
Mail list logo