Hi, Alex.
On 2018/5/1 2:38, Alex Williamson wrote:
> On Fri, 20 Apr 2018 18:07:27 +0800
> "dongbo (E)" wrote:
>
>> From: Dong Bo
>>
>> Signed-off-by: Dong Bo
>> ---
>
> Hi Dong Bo,
>
> The patch is corrupted, please resend and also
From: Dong Bo
Update vfio_add_group_dev description to match the current API.
Signed-off-by: Dong Bo
---
Documentation/vfio.txt | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/Documentation/vfio.txt b/Documentation/vfio.txt
index ef6a511..f1a4d3c 100644
--- a/Documenta
From: Dong Bo
Signed-off-by: Dong Bo
---
Documentation/vfio.txt | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/Documentation/vfio.txt b/Documentation/vfio.txt
index ef6a511..f1a4d3c 100644
--- a/Documentation/vfio.txt
+++ b/Documentation/vfio.txt
@@ -252,15 +252,14 @@
From: Dong Bo
This fixs the following comile warnings with ATA_DEBUG enabled,
which detected by Linaro GCC 5.2-2015.11:
In file included from ./include/linux/printk.h:7:0,
from ./include/linux/kernel.h:14,
from ./include/asm-generic/bug.h:16,
fr
18:01, Catalin Marinas wrote:
>>>>> On Thu, Apr 13, 2017 at 08:33:52PM +0800, dongbo (E) wrote:
>>>>>> From: Dong Bo
>>>>>>
>>>>>> In load_elf_binary(), once the READ_IMPLIES_EXEC flag is set,
>>>>>> the flag
From: Dong Bo
In load_elf_binary(), once the READ_IMPLIES_EXEC flag is set,
the flag is propagated to its child processes, even the elf
files are marked as not requiring executable stack. It may
cause superfluous operations on some arch, e.g.
__sync_icache_dcache on aarch64 due to a PROT_READ mma
From: Dong Bo
Once the READ_IMPLIES_EXEC flag is set on arm64, the flag is
propagated to its child processes, even the ELF files are
marked as not requiring executable stack.
Signed-off-by: Dong Bo
---
arch/arm64/include/asm/elf.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/
On 2017/4/19 18:33, Catalin Marinas wrote:
> On Tue, Apr 18, 2017 at 09:01:52PM +0100, Peter Maydell wrote:
>> On 18 April 2017 at 18:01, Catalin Marinas wrote:
>>> On Thu, Apr 13, 2017 at 08:33:52PM +0800, dongbo (E) wrote:
>>>> From: Dong Bo
>>&g
From: Dong Bo
In load_elf_binary(), once the READ_IMPLIES_EXEC flag is set,
the flag is propagated to its child processes, even the elf
files are marked as not requiring executable stack. It may
cause superfluous operations on some arch, e.g.
__sync_icache_dcache on aarch64 due to a PROT_READ mma
On 2016/7/3 23:27, Pratyush Anand wrote:
> On Tue, Jun 28, 2016 at 1:42 PM, dongbo (E) wrote:
>>
>> From: Dong Bo
>>
>> In designware PCIe driver, the iatu0 is used for both CFG and IO accesses.
>> When sending CFGs to peripherals (e.g. lspci), iatu0 frequent
From: Dong Bo
In designware PCIe driver, the iatu0 is used for both CFG and IO accesses.
When sending CFGs to peripherals (e.g. lspci), iatu0 frequently switches
between CFG and IO alternatively.
A MEMORY probably be sent as an IOs by mistake. Considering the following
configurations:
MEMORY
n 2016/6/27 12:37, Pratyush Anand wrote:
> On Wed, Jun 22, 2016 at 1:54 PM, dongbo (E) wrote:
>> From: Dong Bo
>>
>> In designware PCIe driver, the iatu0 is used for both CFG and IO accesses.
>> When PCIe sends CFGs to peripherals (e.g. lspci),
>> iatu0 frequently
From: Dong Bo
In designware PCIe driver, the iatu0 is used for both CFG and IO accesses.
When PCIe sends CFGs to peripherals (e.g. lspci),
iatu0 frequently switches between CFG and IO alternatively.
If the LIMIT of MEMORY is a value between CFGs BASE_ADDR and IOs LIMIT,
this probably results in
13 matches
Mail list logo
