> From: Anson Huang
> Sent: Thursday, May 14, 2020 2:54 PM
>
> Convert the imx pwm binding to DT schema format using json-schema.
>
> Signed-off-by: Anson Huang
> ---
> Documentation/devicetree/bindings/pwm/imx-pwm.txt | 27 -
> Documentation/devicetree/bindings/pwm/imx-pwm.yaml | 66
Include FMODE_EXEC when building the f_mode field, so that code can
actually test the correct field and values. Only three places actually
examine f_flags for FMODE_EXEC:
fs/open.c: if (unlikely((f->f_mode & FMODE_EXEC) &&
!S_ISREG(inode->i_mode))) {
include/linux/fsnotify.h:
The path_noexec() check, like the regular file check, was happening too
late, letting LSMs see impossible execve()s. Check it earlier as well
and collect the redundant fs/exec.c path_noexec() test under the same
robustness comment as the S_ISREG() check.
My notes on the call path, and related
The execve(2)/uselib(2) syscalls have always rejected non-regular
files. Recently, it was noticed that a deadlock was introduced when trying
to execute pipes, as the S_ISREG() test was happening too late. This was
fixed in commit 73601ea5b7b1 ("fs/open.c: allow opening only regular files
during
Hi,
While looking at the code paths for the proposed O_MAYEXEC flag, I saw
some things that looked like they should be fixed up.
exec: Change uselib(2) IS_SREG() failure to EACCES
This just regularizes the return code on uselib(2).
exec: Relocate S_ISREG() check
This moves
Change uselib(2)' S_ISREG() error return to EACCES instead of EINVAL so
the behavior matches execve(2), and the seemingly documented value.
The "not a regular file" failure mode of execve(2) is explicitly
documented[1], but it is not mentioned in uselib(2)[2] which does,
however, say that open(2)
On 5/18/20 5:47 AM, Paul E. McKenney wrote:
On Fri, May 15, 2020 at 02:36:26PM -0400, Qian Cai wrote:
On May 14, 2020, at 2:13 PM, Paul E. McKenney wrote:
Fair enough! And yes, the Linux kernel is quite large, so I certainly am
not asking you to test the whole thing yourself.
Ok, I saw
On Mon, May 18, 2020 at 07:47:29AM +0200, Mohamed Dawod wrote:
> Fixing some typo errors in traces.h file
>
> Signed-off-by: Mohamed Dawod
> ---
> drivers/staging/wfx/traces.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
What changed from v1? Always put that below the ---
Hi, Andrew,
Andrew Morton writes:
> On Thu, 14 May 2020 15:04:24 +0800 Huang Ying wrote:
>> diff --git a/mm/swapfile.c b/mm/swapfile.c
>> index 35be7a7271f4..9f1343b066c1 100644
>> --- a/mm/swapfile.c
>> +++ b/mm/swapfile.c
>> @@ -746,7 +746,16 @@ static int scan_swap_map_slots(struct
On Sun, May 17, 2020 at 1:48 AM Thomas Gleixner wrote:
>
> Andy Lutomirski writes:
> > On Fri, May 15, 2020 at 5:10 PM Thomas Gleixner wrote:
> >>
> >>
> >> The hardware latency tracer calls into trace_sched_clock and ends up in
> >> various instrumentable functions which is problemeatic vs.
Fixing some typo errors in traces.h file
Signed-off-by: Mohamed Dawod
---
drivers/staging/wfx/traces.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/wfx/traces.h b/drivers/staging/wfx/traces.h
index bb9f7e9..80e131c 100644
---
+ Julien
Hi Lecopzer,
On Sat, 16 May 2020 at 18:20, Lecopzer Chen wrote:
>
> These series implement Perf NMI funxtionality and depends on
> Pseudo NMI [1] which has been upstreamed.
>
> In arm64 with GICv3, Pseudo NMI was implemented for NMI-like interruts.
> That can be extended to Perf NMI
Hi all,
On Mon, 18 May 2020 15:42:40 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the kvm tree got a conflict in:
>
> arch/x86/kvm/svm/svm.c
>
> between commit:
>
> 9f24847d8fdb ("kvm/svm: Disable KCSAN for svm_vcpu_run()")
>
> from the rcu tree and commits:
>
>
On Mon, May 18, 2020 at 2:16 AM Cong Wang wrote:
>
> On Sat, May 16, 2020 at 9:16 AM Subhashini Rao Beerisetty
> wrote:
> > Yes, those are out-of-tree modules. Basically, my question is, in
> > general what is the difference between 'general protection fault' and
> > 'Oops' failure in kernel
Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
arch/x86/kvm/svm/svm.c
between commit:
9f24847d8fdb ("kvm/svm: Disable KCSAN for svm_vcpu_run()")
from the rcu tree and commits:
a9ab13ff6e84 ("KVM: X86: Improve latency for single target IPI fastpath")
404d5d7bff0d
This code was using get_user_pages*(), in a "Case 2" scenario
(DMA/RDMA), using the categorization from [1]. That means that it's
time to convert the get_user_pages*() + put_page() calls to
pin_user_pages*() + unpin_user_pages() calls.
There is some helpful background in [2]: basically, this is a
The Gigabyte X570 Aorus Xtreme motherboard with ALC1220 codec
requires a similar workaround for Clevo laptops to enforce the
DAC/mixer connection path. Set up a quirk entry for that.
BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=205275
Signed-off-by: Christian Lachner
---
The Gigabyte X570 Aorus Xtreme motherboard with ALC1220 codec
requires a similar workaround for Clevo laptops to enforce the
DAC/mixer connection path. This patch sets up a quirk entry for
that. It was successfully tested by a user on BugZilla (see BugLink).
BugLink:
On Fri, May 15, 2020 at 06:49:16PM -0700, Eric Biggers wrote:
> On Tue, May 12, 2020 at 10:43:17PM -0700, ira.we...@intel.com wrote:
> > From: Ira Weiny
> >
> > Verity and DAX are incompatible. Changing the DAX mode due to a verity
> > flag change is wrong without a corresponding
> Subject: RE: [PATCH] dt-bindings: pwm: Convert mxs pwm to json-schema
>
> > +title: Freescale MXS PWM controller
> > +
> > +maintainers:
> > + - Shawn Guo
> > + - Anson Huang
> > +
> > +properties:
> > + compatible:
> > +enum:
> > + - fsl,imx23-pwm
> > +
> > + reg:
> > +
According to the 8021q standard, the VLAN id range is 1 to 4095.
But in the register_vlan_device function, the range is 1 to 4094,
because ">= VLAN_VID_MASK" is used to determine whether the id
is illegal. This will prevent the creation of the vlan4095 interface:
$ vconfig add sit0 4095
> +title: Freescale MXS PWM controller
> +
> +maintainers:
> + - Shawn Guo
> + - Anson Huang
> +
> +properties:
> + compatible:
> +enum:
> + - fsl,imx23-pwm
> +
> + reg:
> +maxItems: 1
> +
> + "#pwm-cells":
> +const: 3
Seems you missed the reference to pwm.yaml.
Regards
> Subject: RE: [PATCH] dt-bindings: interrupt-controller: Convert imx irqsteer
> to
> json-schema
>
> ...
> > +
> > +title: Freescale IRQSTEER Interrupt multiplexer
> > +
> > +maintainers:
> > + - Lucas Stach
> > +
> > +properties:
> > + compatible:
> > +const: fsl,imx-irqsteer
>
> You
On 13.05.20 15:32, Marek Szyprowski wrote:
The Documentation/DMA-API-HOWTO.txt states that the dma_map_sg() function
returns the number of the created entries in the DMA address space.
However the subsequent calls to the dma_sync_sg_for_{device,cpu}() and
dma_unmap_sg must be called with the
Hi all,
On Mon, 20 Apr 2020 19:41:56 -0700 John Stultz wrote:
>
> On Mon, Apr 20, 2020 at 4:29 PM Stephen Rothwell
> wrote:
> >
> > On Tue, 14 Apr 2020 18:18:11 -0700 John Stultz
> > wrote:
> > >
> > > On Tue, Apr 14, 2020 at 5:41 PM Stephen Rothwell
> > > wrote:
> > > >
> > > > After
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
include/linux/compiler.h
between commit:
a9a3ed1eff36 ("x86: Fix early boot crash on gcc-10, third try")
from Linus' tree and commit:
f670269a42bf ("x86: Fix early boot crash on gcc-10, next try")
from the tip tree.
On mips platform, hw PTE entry valid bit is set in pte_mkyoung
function, it is used to set physical page with readable privilege.
Here add pte_mkyoung function to make page readable on MIPS platform
during page fault handling. This patch improves page fault latency
about 10% on my MIPS machine
If two threads concurrently fault at the same address, the thread that
won the race updates the PTE and its local TLB. For now, the other
thread gives up, simply does nothing, and continues.
It could happen that this second thread triggers another fault, whereby
it only updates its local TLB
It is not necessary to flush tlb page on all CPUs if suitable PTE
entry exists already during page fault handling, just updating
TLB is fine.
Here redefine flush_tlb_fix_spurious_fault as empty on MIPS system.
Change in v2:
- split flush_tlb_fix_spurious_fault and tlb update into two patches
-
Hi Xu,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on clk/clk-next]
[also build test WARNING on v5.7-rc6 next-20200515]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base'
Fixes: 52e7c52d2ded ("RISC-V: Stop relying on GCC's register allocator's
hueristics")
Signed-off-by: kbuild test robot
---
process.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/riscv/kernel/process.c b/arch/riscv/kernel/process.c
index
On Fri, May 15, 2020 at 07:02:53PM -0700, Eric Biggers wrote:
> On Tue, May 12, 2020 at 10:43:18PM -0700, ira.we...@intel.com wrote:
> > From: Ira Weiny
> >
> > Encryption and DAX are incompatible. Changing the DAX mode due to a
> > change in Encryption mode is wrong without a corresponding
> >
20. 5. 16. 오후 7:57에 Christophe JAILLET 이(가) 쓴 글:
> 'exynos_dsi_parse_dt()' takes a reference to 'dsi->in_bridge_node'.
> This must be released in the error handling path.
Picked it up.
Thanks,
Inki Dae
>
> In order to do that, add an error handling path and move the
>
Hi Linus,
This is exfat fixes pull request for v5.7-rc7. I add description of
this pull request on below. Please pull exfat with following fixes.
Thanks!
The following changes since commit b9bbe6ed63b2b9f2c9ee5cbd0f2c946a2723f4ce:
Linux 5.7-rc6 (2020-05-17 16:48:37 -0700)
are available in
Hi all,
After merging the keys tree, today's linux-next build (x86_64
allmodconfig) failed like this:
x86_64-linux-gnu-ld: security/keys/big_key.o: in function `big_key_read':
big_key.c:(.text+0x562): undefined reference to `chacha20poly1305_decrypt'
x86_64-linux-gnu-ld: security/keys/big_key.o:
On 2020-05-17 13:46 +0800, Xiangyang Zhang wrote:
> DMA not unmapped when lock failed, this patch fixed it.
>
Fixes: 4322c5bee85e ("qlge: Expand coverage of hw lock for config register.")
> Signed-off-by: Xiangyang Zhang
> ---
> drivers/staging/qlge/qlge_main.c | 3 ++-
> 1 file changed, 2
On 5/6/2020 5:44 PM, Paolo Bonzini wrote:
Using CPUID data can be useful for the processor compatibility
check, but that's it. Using it to compute guest-reserved bits
can have both false positives (such as LA57 and UMIP which we
are already handling) and false negatives:
in particular, with
On Sun, May 17, 2020 at 11:56:08PM +0200, Heiko Stuebner wrote:
> @@ -1457,6 +1458,7 @@ void serial8250_em485_stop_tx(struct uart_8250_port *p)
>* Enable previously disabled RX interrupts.
>*/
> if (!(p->port.rs485.flags & SER_RS485_RX_DURING_TX)) {
> +
Add a named pipe as an exec target to make sure that non-regular
files are rejected by execve() with EACCES. This can help verify
commit 73601ea5b7b1 ("fs/open.c: allow opening only regular files
during execve()").
Signed-off-by: Kees Cook
---
tools/testing/selftests/exec/.gitignore | 1 +
This fixes the issue of driver not getting auto loaded with
MODULE_ALIAS.
With this patch:
$find /sys/devices -name modalias -print0 | xargs -0 grep -i acp3x
/sys/devices/pci:00/:00:08.1/:03:00.5/acp3x_i2s_playcap.2/
modalias:platform:acp3x_i2s_playcap
>
> I tried to imagine a negative impact for this hw_ptr_jiffies update when the
> DMA position is not updated from the driver and I haven't found any so far.
>
> Let's apply this and we'll see in future :-)
>
> And yes, the patch description should be improved (DMA ptr is not updated /
>
There is a corner case that ALSA keeps increasing the hw_ptr but DMA
already stop working/updating the position for a long time.
In following log we can see the position returned from DMA driver does
not move at all but the hw_ptr got increased at some point of time so
snd_pcm_avail() will return
On Sun, May 17, 2020 at 08:49:39PM -0700, Ira Weiny wrote:
> On Sat, May 16, 2020 at 03:33:06PM -0700, Guenter Roeck wrote:
> > On Thu, May 07, 2020 at 07:59:55AM -0700, ira.we...@intel.com wrote:
> > > From: Ira Weiny
> > >
> > > Every single architecture (including !CONFIG_HIGHMEM) calls...
>
Hi all,
After merging the mmc tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
WARNING: modpost: missing MODULE_LICENSE() in
drivers/mmc/host/meson-mx-sdhc-clkc.o
see include/linux/module.h for more information
ERROR: modpost: "meson_mx_sdhc_register_clkc"
On 5/13/20 7:56 PM, Nikhil Mahale wrote:
> On 3/20/20 3:16 AM, Michael Kelley wrote:
>> From: Arnd Bergmann Sent: Wednesday, March 18, 2020 2:27 AM
>>>
>>> On Wed, Mar 18, 2020 at 1:18 AM Michael Kelley
>>> wrote:
From: Arnd Bergmann
> On Sat, Mar 14, 2020 at 4:36 PM Michael Kelley
On 05/11/2020 05:55 PM, Zhenyu Ye wrote:
> On 2020/5/5 18:14, Mark Rutland wrote:
>> On Tue, Apr 14, 2020 at 07:28:34PM +0800, Zhenyu Ye wrote:
>>> ARMv8.4-TLBI provides TLBI invalidation instruction that apply to a
>>> range of input addresses. This patch detect this feature.
>>>
>>>
On 5/16/20 12:47 AM, Hushijie wrote:
>> On 5/14/20 7:31 AM, Shijie Hu wrote:
>>> + if (mm->get_unmapped_area == arch_get_unmapped_area)
>>> + return hugetlb_get_unmapped_area_bottomup(file, addr, len,
>>> + pgoff, flags);
>>> + return
How are you and your family? my name is Prashant Wong Lin,
i am a native of Hong Kong but resides and a citizen of United Kingdom.
I work with an Oil and Gas Company here in London, tell me about you? Your work
etc
--
This email has been checked for viruses by Avast antivirus software.
This code was using get_user_pages*(), in a "Case 2" scenario
(DMA/RDMA), using the categorization from [1]. That means that it's
time to convert the get_user_pages*() + put_page() calls to
pin_user_pages*() + unpin_user_pages() calls.
There is some helpful background in [2]: basically, this is a
发件人：Liviu Dudau
发送日期：2020-05-15 22:41:49
收件人：Bernard
抄送人：Brian Starkey ,David Airlie
,Daniel Vetter
,dri-de...@lists.freedesktop.org,linux-kernel@vger.kernel.org,opensource.ker...@vivo.com
主题：Re: Re:Re: [PATCH v2] drm/arm: fixes pixel clock enabled with wrong
format>Hi Bernard,
>
>On Fri,
On Sun, Apr 26, 2020 at 07:47:49PM +0200, Michał Mirosław wrote:
> Add information found in downstream kernels, to make the code less
> magic.
>
> Signed-off-by: Michał Mirosław
> Reviewed-by: Dmitry Osipenko
> Tested-by: Dmitry Osipenko
> ---
> drivers/input/touchscreen/elants_i2c.c | 29
On Sun, Apr 26, 2020 at 07:47:52PM +0200, Michał Mirosław wrote:
> From: Dmitry Osipenko
>
> eKTF3624 touchscreen firmware uses two variants of the reply opcodes for
> reporting touch events: one is 0x63 (used by older firmware) and other is
> 0x66 (used by newer firmware). The 0x66 variant is
On Sun, Apr 26, 2020 at 07:47:51PM +0200, Michał Mirosław wrote:
> Apply some DRY-ing to elants_i2c_execute_command() callers. This pulls
> polling and error printk()s into a single function.
>
> Signed-off-by: Michał Mirosław
Applied, thank you.
--
Dmitry
On Sun, Apr 26, 2020 at 07:47:51PM +0200, Michał Mirosław wrote:
> Allow overriding of information from hardware and support additional
> common DT properties like axis inversion. This is required for eg.
> Nexus 7 and TF300T where the programmed values in firmware differ
> from reality.
>
>
Hi Steve,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on asoc/for-next]
[also build test WARNING on v5.7-rc6 next-20200515]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base'
Move watchdog syscl interface to watchdog.c.
Use register_sysctl() to register the sysctl interface to avoid
merge conflicts when different features modify sysctl.c at the same time.
Signed-off-by: Xiaoming Ni
Reviewed-by: Kees Cook
---
kernel/sysctl.c | 96
Kernel/sysctl.c contains more than 190 interface files, and there are a
large number of config macro controls. When modifying the sysctl
interface directly in kernel/sysctl.c, conflicts are very easy to occur.
E.g: https://lkml.org/lkml/2020/5/10/413.
Use register_sysctl() to register the
Move hung_task sysctl interface to hung_task.c.
Use register_sysctl() to register the sysctl interface to avoid
merge conflicts when different features modify sysctl.c at the same time.
Signed-off-by: Xiaoming Ni
Reviewed-by: Kees Cook
---
include/linux/sched/sysctl.h | 8 +-
In order to eliminate the duplicate code for registering the sysctl
interface during the initialization of each feature, add the
register_sysctl_init() interface
Signed-off-by: Xiaoming Ni
Reviewed-by: Kees Cook
---
include/linux/sysctl.h | 2 ++
kernel/sysctl.c| 19
Some boundary (.extra1 .extra2) constants (E.g: neg_one two) in
sysctl.c are used in multiple features. Move these variables to
sysctl_vals to avoid adding duplicate variables when cleaning up
sysctls table.
Signed-off-by: Xiaoming Ni
Reviewed-by: Kees Cook
---
fs/proc/proc_sysctl.c | 2 +-
On Mon, 2020-05-18 at 03:46 +, Xu Wang wrote:
> devm_kasprintf() may fail, so we should better add a NULL check
> and propagate an error on failure.
You didn't compile this.
All the return values of this function are already checked.
> Signed-off-by: Xu Wang
> ---
> drivers/clk/ti/adpll.c
On Sun, May 17, 2020 at 7:51 PM Baolin Wang wrote:
>
> The flush_queue_delayed was introdued to hold queue if flush is
> running for non-queueable flush drive by commit 3ac0cc450870
> ("hold queue if flush is running for non-queueable flush drive"),
> but the non mq parts of the flush code had
On Sat, May 16, 2020 at 03:33:06PM -0700, Guenter Roeck wrote:
> On Thu, May 07, 2020 at 07:59:55AM -0700, ira.we...@intel.com wrote:
> > From: Ira Weiny
> >
> > Every single architecture (including !CONFIG_HIGHMEM) calls...
> >
> > pagefault_enable();
> > preempt_enable();
> >
> > ...
devm_kasprintf() may fail, so we should better add a NULL check
and propagate an error on failure.
Signed-off-by: Xu Wang
---
drivers/clk/ti/adpll.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/clk/ti/adpll.c b/drivers/clk/ti/adpll.c
index bb2f283..f18a672 100644
---
> From: Anson Huang
> Sent: Friday, May 15, 2020 8:58 PM
>
> Use __maybe_unused for power management related functions to simplify the
> code.
>
> Signed-off-by: Anson Huang
Reviewed-by: Dong Aisheng
Regards
Aisheng
> ---
> drivers/tty/serial/fsl_lpuart.c | 6 ++
> 1 file changed, 2
On Wed, Apr 29, 2020 at 04:20:51PM +0800, Shawn Guo wrote:
> -Original Message-
> From: Shawn Guo
> Sent: 2020年5月17日 22:10
> To: Qiang Zhao
> Cc: Leo Li ; devicet...@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [patch v2 1/2] ls1043ardb: add qe node to ls1043ardb
>
>
...
> +
> +title: Freescale IRQSTEER Interrupt multiplexer
> +
> +maintainers:
> + - Lucas Stach
> +
> +properties:
> + compatible:
> +const: fsl,imx-irqsteer
You changed binding here without comments?
Regards
Aisheng
> +
> + reg:
> +maxItems: 1
> +
> + interrupts:
> +
On Sun, Apr 26, 2020 at 07:47:50PM +0200, Michał Mirosław wrote:
> Driver only ever reports MT events and input_mt_init_slots() sets up
> emulated axes already. Clear the capabilities not generated directly
> and move MT axes setup, so they are visible by input_mt_init_slots().
>
>
On 05/16/2020 05:34 PM, maobibo wrote:
>
>
> On 05/15/2020 09:50 PM, David Hildenbrand wrote:
>> On 14.05.20 08:50, Bibo Mao wrote:
>>> If there are two threads hitting page fault at the address, one
>>> thread updates pte entry and local tlb, the other thread can update
>>> local tlb also,
Hi Jiri,
On 5/15/2020 4:33 PM, Jiri Olsa wrote:
On Fri, May 15, 2020 at 02:04:57PM +0800, Jin, Yao wrote:
SNIP
I think I get the root cause. That should be a serious bug in get_group_fd,
access violation!
For a group mixed with system-wide event and per-core event and the group
leader is
On 2020/5/15 下午11:33, Michael S. Tsirkin wrote:
sparse warns about converting void * to void __user *. This is not new
but only got noticed now that vhost is built on more systems.
This is just a question of __user tags missing in a couple of places,
so fix it up.
Fixes: f88949138058 ("vhost:
Hello,
syzbot found the following crash on:
HEAD commit:24085f70 Merge tag 'trace-v5.7-rc4' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=117087fa10
kernel config: https://syzkaller.appspot.com/x/.config?x=efdde85c3af536b5
Added an irq type VFIO_IRQ_TYPE_REMAP_BAR_REGION to
dynamically query and remap BAR regions.
QEMU decodes the index of the BARs by reading cnt of eventfd.
If bit n is set, the corresponding BAR will be requeried and
its subregions will be remapped according to the its new flags.
rely on [1]
This patch gives an example implementation to support vendor defined
irq_type.
- on this vendor driver open, it registers an irq of type
VFIO_IRQ_TYPE_REMAP_BAR_REGION, and reports to driver vfio-pci there's
1 vendor irq.
- after userspace detects and enables the irq of type
This patch let the vendor driver register a migration region, so that
the migration detection code in userspace will be able to see this
region and triggers the migration flow according to VFIO migration
protocol.
This migration region works based on VFIO migration series with some
minor fixes:
This driver intercepts all device operations as long as it's probed
successfully by vfio-pci driver.
It will process regions and irqs of its interest and then forward
operations to default handlers exported from vfio pci if it wishes to.
In this patch, this driver does nothing but pass through
Fix up one typos @nev -> @nr_irqs.
Cc: Marc Zyngier
Signed-off-by: Shaokun Zhang
---
drivers/base/platform-msi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/base/platform-msi.c b/drivers/base/platform-msi.c
index 8da314b81eab..c4a17e5edf8b 100644
---
This is a virtual irq type.
vendor driver triggers this irq when it wants to notify userspace to
remap PCI BARs.
1. vendor driver triggers this irq and packs the target bar number in
the ctx count. i.e. "1 << bar_number".
if a bit is set, the corresponding bar is to be remapped.
2.
From: Tina Zhang
Cap the number of irqs with fixed indexes and use capability chains
to chain device specific irqs.
v2:
- Irq capability index starts from 1.
Signed-off-by: Tina Zhang
Signed-off-by: Eric Auger
---
include/uapi/linux/vfio.h | 19 ++-
1 file changed, 18
This allows vendor driver to read/write to bars directly which is useful
in security checking condition.
Cc: Kevin Tian
Signed-off-by: Yan Zhao
---
drivers/vfio/pci/vfio_pci_rdwr.c | 10 ++
include/linux/vfio.h | 1 +
2 files changed, 11 insertions(+)
diff --git
This allows a simpler VFIO_DEVICE_GET_INFO ioctl in vendor driver
Cc: Kevin Tian
Signed-off-by: Yan Zhao
---
drivers/vfio/pci/vfio_pci.c | 23 +--
drivers/vfio/pci/vfio_pci_private.h | 2 ++
include/linux/vfio.h| 3 +++
3 files changed, 26
export functions vfio_pci_vendor_data(), vfio_pci_irq_type(),
vfio_pci_num_regions(), vfio_pci_pdev(), and functions in vfio_pci_ops,
so they are able to be called from outside modules and make them a kind of
inherited by vfio_device_ops provided by vendor modules
Cc: Kevin Tian
Suggested-by:
vendor modules call macro module_vfio_pci_register_vendor_handler to
generate module_init and module_exit.
It is necessary to ensure that vendor modules always call
vfio_pci_register_vendor_driver() on driver loading and
vfio_pci_unregister_vendor_driver on driver unloading,
because
(1) at
Add Ethernet interrupt details to the WeTek Hub/Play2 dtsi to resolve
an issue with Ethernet probing in mainline u-boot.
Signed-off-by: Christian Hewitt
---
arch/arm64/boot/dts/amlogic/meson-gxbb-wetek.dtsi | 4
1 file changed, 4 insertions(+)
diff --git
vfio_pci_vendor_driver_ops includes two parts:
(1) .probe() and .remove() interface to be called by vfio_pci_probe()
and vfio_pci_remove().
(2) pointer to struct vfio_device_ops. It will be registered as ops of vfio
device if .probe() succeeds.
Suggested-by: Alex Williamson
Signed-off-by: Yan
When using vfio-pci to pass through devices, though it's desired to use
its default implementations in most of time, it is also sometimes
necessary to call vendors specific operations.
For example, in order to do device live migration, the way of dirty
pages detection and device state save-restore
On Mon, 18 May 2020 at 09:32, Haiwei Li wrote:
>
> From: Haiwei Li
>
> There is a bad indentation in next branch. The patch looks like
> fixes nothing though it fixes the indentation.
>
> Before fixing:
>
> if (!handle_fastpath_set_x2apic_icr_irqoff(vcpu, data)) {
>
>Hi,
>
>On Fri, 2020-05-15 at 09:11 -0400, Steven Rostedt wrote:
>> It's best to Cc the maintainers of the file. Nobody reads linux-
>> kernel (it
>> produces 800 emails a day!). Luckily, I happen to monitor the
>> linux-trace-devel list (which is mostly for userland tools),
>> otherwise this
>>
With Clang 9.0.1,
return array->value + array->elem_size * (index & array->index_mask);
but array->value is,
char value[0] __aligned(8);
[ 506.031548][ T4134] LTP: starting bpf_prog02
[ 506.125326][ T4352]
[
On 5/16/20 8:27 PM, Balbir Singh wrote:
On 14/5/20 10:00 pm, Matthew Wilcox wrote:
On Thu, May 14, 2020 at 09:00:40PM +1000, Balbir Singh wrote:
I wonder if the right thing to do is also to disable pre-emption, just so that
the thread does not linger on with sensitive data.
void
On 2020/5/18 09:08, Tiezhu Yang wrote:
On 05/16/2020 07:09 PM, WANG Xuerui wrote:
On 5/16/20 3:03 PM, Tiezhu Yang wrote:
After commit 87fcfa7b7fe6 ("MIPS: Loongson64: Add generic dts"),
there already exists the node and property of Loongson CPU UART0
in loongson3-package.dtsi:
cpu_uart0:
The Shenzen AZW (Beelink) GT-King Pro is based on the Amlogic W400
reference board with an S922X chip.
- 4GB LPDDR4 RAM
- 64GB eMMC storage
- 10/100/1000 Base-T Ethernet
- AP6356S Wireless (802.11 a/b/g/n/ac, BT 4.1)
- HDMI 2.1 video
- Analogue audio output
- 1x RS232 port
- 2x USB 2.0 port
- 2x
The Shenzen AZW (Beelink) GT-King Pro is based on the Amlogic W400 reference
board with an S922X chip.
Acked-by: Rob Herring
Signed-off-by: Christian Hewitt
---
Documentation/devicetree/bindings/arm/amlogic.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git
The Shenzen AZW (Beelink) GT-King is based on the Amlogic W400 reference
board with an S922X chip.
- 4GB LPDDR4 RAM
- 64GB eMMC storage
- 10/100/1000 Base-T Ethernet
- AP6356S Wireless (802.11 a/b/g/n/ac, BT 4.1)
- HDMI 2.1 video
- S/PDIF optical output
- Analogue audio output
- 1x USB 2.0 port
-
The Shenzen AZW (Beelink) GT-King is based on the Amlogic W400 reference
board with an S922X chip.
Acked-by: Rob Herring
Signed-off-by: Christian Hewitt
---
Documentation/devicetree/bindings/arm/amlogic.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git
Convert the Ugoos AM6 dts into meson-g12b-w400.dtsi, and then create
a new AM6 dts that references it. This is in preparation for several
new G12B devices that will share the common w400 dtsi.
Signed-off-by: Christian Hewitt
---
.../boot/dts/amlogic/meson-g12b-ugoos-am6.dts | 410
This series combines patch 2 from [1] which converts the existing Ugoos
AM6 device-tree to a common W400 dtsi and dts, and then reworks the
Beelink GT-King/GT-King Pro serries from [2] to use the dtsi, but this
time without the offending common audio dtsi approach. I've carried
forwards acks on
Hi all,
Today's linux-next merge of the jc_docs tree got a conflict in:
kernel/sysctl.c
between commit:
f461d2dcd511 ("sysctl: avoid forward declarations")
from the vfs tree and commit:
2f4c33063ad7 ("docs: sysctl/kernel: document ngroups_max")
from the jc_docs tree.
I fixed it up
The Shenzen AZW (Beelink) GT-King Pro is based on the Amlogic W400
reference board with an S922X chip.
- 4GB LPDDR4 RAM
- 64GB eMMC storage
- 10/100/1000 Base-T Ethernet
- AP6356S Wireless (802.11 a/b/g/n/ac, BT 4.1)
- HDMI 2.1 video
- Analogue audio output
- 1x RS232 port
- 2x USB 2.0 port
- 2x
On 2020/5/16 9:04, Jaegeuk Kim wrote:
> When parsing the mount option, we don't have sbi->user_block_count.
> Should do it after getting it.
>
> Signed-off-by: Jaegeuk Kim
Reviewed-by: Chao Yu
Thanks,
1 - 100 of 453 matches
Mail list logo
