copy_{to,from}_user() returns the amount left to copy, it should return
-EFAULT error code if copy {to,from} user failed, just like the return
value is an error code when {put,get}_user() failed, this is to make the
return value consistent, no function change.
Signed-off-by: Tiezhu Yang
---
On 6/3/21 11:55 am, Lukas Bulwahn wrote:
> On Sat, Mar 6, 2021 at 5:35 AM Matthew Wilcox wrote:
>>
>> On Thu, Feb 25, 2021 at 08:20:33PM +0530, Aditya Srivastava wrote:
>>> +++ b/scripts/kernel-doc
>>> @@ -1201,12 +1201,23 @@ sub dump_union($$) {
>>> sub dump_struct($$) {
>>> my $x = shift;
Hello,
syzbot found the following issue on:
HEAD commit:d01b59c9 bpf: Add bpf_skb_adjust_room flag BPF_F_ADJ_ROOM_..
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1592bd66d0
kernel config: https://syzkaller.appspot.com/x/.config?x=66df2ca4f2dd3022
Hello,
syzbot found the following issue on:
HEAD commit:ad5d07f4 cipso,calipso: resolve a number of problems with ..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=12aca7cad0
kernel config: https://syzkaller.appspot.com/x/.config?x=402784bff477e1ac
On 03/06/2021 10:36 AM, Qing Zhang wrote:
Add default config for 2K1000.
Signed-off-by: Jiaxun Yang
Signed-off-by: Qing Zhang
Tested-by: Ming Wang
Thanks,
Ming
On 03/06/2021 10:36 AM, Qing Zhang wrote:
Add liointc-2.0 properties support, so update the maxItems and description.
Signed-off-by: Jiaxun Yang
Signed-off-by: Qing Zhang
Tested-by: Ming Wang
Thanks,
Ming
On 03/06/2021 10:36 AM, Qing Zhang wrote:
Add IO interrupt controller support for Loongson 2k1000, different
from the 3a series is that 2K1000 has 64 interrupt sources, 0-31
correspond to the device tree liointc0 device node, and the other
correspond to liointc1 node.
Signed-off-by: Jiaxun
On 03/06/2021 10:36 AM, Qing Zhang wrote:
Distinguish between 3A series CPU and 2K1000 CPU UART0.
Signed-off-by: Jiaxun Yang
Signed-off-by: Qing Zhang
Tested-by: Ming Wang
Thanks,
Ming
On 03/06/2021 10:36 AM, Qing Zhang wrote:
Get the fixed-clock from the CPU0 node of the device tree.
Signed-off-by: Jiaxun Yang
Signed-off-by: Qing Zhang
Tested-by: Ming Wang
Thanks,
Ming
On 03/06/2021 10:36 AM, Qing Zhang wrote:
Add DTB boot support, only support LS2K1000 processor for now,
determine whether to use the built-in DTB or the DTB from the
firmware by checking the range of CKSEG0 and XKPHYS.loongson_fw
_interface will be used in the future.
Signed-off-by: Jiaxun
On 03/06/2021 10:36 AM, Qing Zhang wrote:
Add DeviceTree files for Loongson 2K1000 processor,currently only
supports single-core boot.
Signed-off-by: Jiaxun Yang
Signed-off-by: Qing Zhang
Tested-by: Ming Wang
Thanks,
Ming
Hi Rob,
On Fri, Mar 5, 2021 at 11:47 PM Rob Herring wrote:
[snip]
> > +
> > + ralink,sysctl:
> > +$ref: /schemas/types.yaml#/definitions/phandle
> > +description:
> > + phandle of syscon used to control system registers
> > +
> > + ralink,memctl:
> > +$ref:
From: Junlin Yang
fixes three typos found by codespell.
Signed-off-by: Junlin Yang
---
arch/csky/include/asm/asid.h| 2 +-
arch/csky/include/asm/barrier.h | 2 +-
arch/csky/include/asm/vdso.h| 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git
From: Zhang Yunkai
'proto.h' included in 'traps.c' is duplicated.
Signed-off-by: Zhang Yunkai
---
arch/x86/kernel/traps.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/x86/kernel/traps.c b/arch/x86/kernel/traps.c
index 7f5aec758f0e..cb9b675dc003 100644
---
On Mon, Mar 1, 2021 at 10:34 PM Linus Torvalds
wrote:
>
> On Mon, Mar 1, 2021 at 12:35 AM Sedat Dilek wrote:
> >
> > I wondered why there was approx. for 6 days no commits and got an
> > answer from an LWN posting "5.12 Merge window delayed".
> > Unsure, if there was a posting to LKML?
>
> There
From: Zhang Yunkai
'cpu_device_id.h' and 'intel_family.h' included in 'smpboot.c'
is duplicated. It is also included in the 80th line.
Signed-off-by: Zhang Yunkai
---
arch/x86/kernel/smpboot.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/x86/kernel/smpboot.c
+void ls7a_mm_wreg_locked(struct loongson_device *ldev, u32 offset,
u32 val)
+{
+ unsigned long flags;
+
+ spin_lock_irqsave(ldev-mmio_lock, flags);
+ writel(val, ldev-mmio + offset);
+ spin_unlock_irqrestore(ldev-mmio_lock, flags);
+}
Why lock and disable
On Fri, Mar 5, 2021 at 8:54 PM Sedat Dilek wrote:
>
> On Fri, Mar 5, 2021 at 8:47 PM Alan Stern wrote:
> >
> > On Fri, Mar 05, 2021 at 08:41:40PM +0100, Sedat Dilek wrote:
> > > On Fri, Mar 5, 2021 at 8:30 PM Alan Stern
> > > wrote:
> >
> > > > Okay, that indicates the ATA commands are being
On Fri, Mar 5, 2021 at 8:38 PM Aditya wrote:
>
> On 6/3/21 12:13 am, Matthew Wilcox wrote:
> > On Fri, Mar 05, 2021 at 11:50:00PM +0530, Aditya Srivastava wrote:
> >> Provide a simple fix by adding "__attribute_const__" in the corresponding
> >> regex expression.
> >>
> >> A quick evaluation by
Fixed a struct without const
Signed-off-by: nabil5352
---
drivers/staging/android/ashmem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/android/ashmem.c b/drivers/staging/android/ashmem.c
index d66a64e42273..7854fd410efa 100644
---
On 2021/3/5 20:20, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.10.21 release.
There are 102 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On Sat, Mar 6, 2021 at 5:35 AM Matthew Wilcox wrote:
>
> On Thu, Feb 25, 2021 at 08:20:33PM +0530, Aditya Srivastava wrote:
> > +++ b/scripts/kernel-doc
> > @@ -1201,12 +1201,23 @@ sub dump_union($$) {
> > sub dump_struct($$) {
> > my $x = shift;
> > my $file = shift;
> > +my
Hello,
This is to officially inform you that (ATM Card number:5199 1107 2037
2066) has been accredited in your favor. Your Personal Identification
Number is 5199. The ATM Card Value is US$10,000,000.00.You are advised
to contact me with the following information: Name, Address,Mobile No,
Age and
Quoting Elliot Berman (2021-03-05 10:18:09)
> On 3/3/2021 10:14 PM, Stephen Boyd wrote:
> > Quoting Elliot Berman (2021-03-03 19:35:08)
> >>
> >> On 2/23/2021 1:45 PM, Stephen Boyd wrote:
> >>> These scm calls are never used outside of legacy ARMv7 based platforms.
> >>> That's because PSCI,
Move $(strip ...) to the callee from the callers of suffix-search. It
shortens the code slightly. Adding a space after a comma will not be
a matter. I also dropped parentheses from single character variables.
Signed-off-by: Masahiro Yamada
---
scripts/Makefile.lib | 6 +++---
1 file changed, 3
I think multi-obj-* is clearer, and more consisten with real-obj-*.
Rename as follows:
multi-used-y -> multi-obj-y
multi-used-m -> multi-obj-m
multi-used-> multi-obj-ym
Signed-off-by: Masahiro Yamada
---
scripts/Makefile.build | 6 +++---
scripts/Makefile.lib | 10
On Wed, Mar 3, 2021 at 1:36 PM Viresh Kumar wrote:
>
> From: Rob Herring
>
> Add a generic rule to apply fdtoverlay in Makefile.lib, so every
> platform doesn't need to carry the complex rule.
>
> The platform's Makefile only needs to have this now:
>
> DTC_FLAGS_foo_base += -@
> foo-dtbs :=
On Sat, Mar 6, 2021 at 3:00 AM Roman Gushchin wrote:
>
> On Wed, Mar 03, 2021 at 01:59:14PM +0800, Muchun Song wrote:
> > We want to reuse the obj_cgroup APIs to charge the kmem pages when
> > If we do that, we should store an object cgroup pointer to
> > page->memcg_data for the kmem pages.
> >
On 6.3.2021 3.13, Andrew Morton wrote:
On Mon, 15 Feb 2021 22:26:34 +0200 Topi Miettinen wrote:
Memory mappings inside kernel allocated with vmalloc() are in
predictable order and packed tightly toward the low addresses, except
for per-cpu areas which start from top of the vmalloc area. With
The constants in enum sbi_ext_rfence_fid should match the SBI
specification. See
https://github.com/riscv/riscv-sbi-doc/blob/master/riscv-sbi.adoc#78-function-listing
| Function Name | FID | EID
| sbi_remote_fence_i | 0 | 0x52464E43
| sbi_remote_sfence_vma | 1 |
On 3/5/2021 4:20 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.21 release.
> There are 102 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On Sat, Mar 6, 2021 at 2:56 AM Roman Gushchin wrote:
>
> On Wed, Mar 03, 2021 at 01:59:13PM +0800, Muchun Song wrote:
> > We know that the unit of slab object charging is bytes, the unit of
> > kmem page charging is PAGE_SIZE. If we want to reuse obj_cgroup APIs
> > to charge the kmem pages, we
On 3/5/2021 4:21 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.4.103 release.
> There are 72 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 3/4/2021 6:05 PM, Bhaskar Chowdhury wrote:
>
>
> s/revelant/relevant/
>
> Signed-off-by: Bhaskar Chowdhury
Acked-by: Florian Fainelli
Previous changes to this file/directory usually used MIPS: BCM63XX: as a
subject prefix, maybe Thomas can fix it up while applying for consistency.
On 3/5/2021 4:22 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.260 release.
> There are 41 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
Hi Guenter,
On Fri, Mar 05, 2021 at 07:18:47PM -0800, Guenter Roeck wrote:
> On Fri, Mar 05, 2021 at 03:52:58AM -0600, Gustavo A. R. Silva wrote:
> > In preparation to enable -Wimplicit-fallthrough for Clang, fix a warning
> > by explicitly adding a break statement instead of letting the code
> From: Rob Herring
> Sent: Friday, March 5, 2021 10:14 PM
>
> On Fri, Mar 5, 2021 at 8:09 AM Aisheng Dong
> wrote:
> >
> > Hi Rob,
> >
> > > From: Peng Fan (OSS)
> > > Sent: Thursday, February 25, 2021 11:10 AM
> > >
> > > From: Peng Fan
> > >
> > > Add clock bindings for fsl-imx-esdhc yaml
__must_be_array, offsetof, sizeof_field and __stringify are all
preprocessor macros and do not evaluate their arguments. As such, it
is safe not to warn when arguments are being reused in those four
sub-expressions.
Exclude those so that they can pass checkpatch.
Signed-off-by: Vincent Mailhol
On 3/5/21 7:14 AM, John Garry wrote:
> diff --git a/block/blk-mq-tag.c b/block/blk-mq-tag.c
> index 7ff1b20d58e7..5950fee490e8 100644
> --- a/block/blk-mq-tag.c
> +++ b/block/blk-mq-tag.c
> @@ -358,11 +358,16 @@ void blk_mq_tagset_busy_iter(struct blk_mq_tag_set
> *tagset,
> {
> int i;
>
On Thu, Feb 25, 2021 at 08:20:33PM +0530, Aditya Srivastava wrote:
> +++ b/scripts/kernel-doc
> @@ -1201,12 +1201,23 @@ sub dump_union($$) {
> sub dump_struct($$) {
> my $x = shift;
> my $file = shift;
> +my $decl_type;
> +my $members;
> +my $type = qr{struct|union};
> +
On 3/5/21 7:14 AM, John Garry wrote:
> diff --git a/block/blk.h b/block/blk.h
> index 3b53e44b967e..1a948bfd91e4 100644
> --- a/block/blk.h
> +++ b/block/blk.h
> @@ -201,10 +201,29 @@ void elv_unregister_queue(struct request_queue *q);
> static inline void elevator_exit(struct request_queue *q,
>
On 3/4/2021 5:08 PM, Vladimir Oltean wrote:
> On Tue, Mar 02, 2021 at 07:37:34PM -0800, Florian Fainelli wrote:
>> Took a while but for the 54210E reference board here are the numbers,
>> your mileage will vary depending on the supplies, regulator efficiency
>> and PCB design around the PHY
Thx,
Looks good to me, Signed-off-by.
On Sat, Mar 6, 2021 at 11:23 AM angkery wrote:
>
> From: Junlin Yang
>
> fixes three typos found by codespell.
>
> Signed-off-by: Junlin Yang
> ---
> arch/csky/include/asm/asid.h| 2 +-
> arch/csky/include/asm/barrier.h | 2 +-
>
From: Gao Xiang
Martin reported an issue that directory read could be hung on the
latest -rc kernel with some certain image. The root cause is that
commit baa2c7c97153 ("block: set .bi_max_vecs as actual allocated
vector number") changes .bi_max_vecs behavior. bio->bi_max_vecs
is set as actual
On Fri 05 Mar 15:35 CST 2021, Caleb Connolly wrote:
Please add "qcom: " to $subject as well.
> Add a minimal devicetree capable of booting on the Pixel 2 XL MSM8998
> device.
>
> It's currently possible to boot the device into postmarketOS with USB
> networking, however the display panel
> I am proposing acceptance of a commonly used implementation for accessing
> SFPs because the one used by the netdev/netlink community does not fit the
> architecture of the white box NOS/switch community.
Please could you expand on this. I've given suggests as to how the new
netlink KAPI could
From: Gao Xiang
Martin reported an issue that directory read could be hung on the
latest -rc kernel with some certain image. The root cause is that
commit baa2c7c97153 ("block: set .bi_max_vecs as actual allocated
vector number") changes .bi_max_vecs behavior. bio->bi_max_vecs
is set as actual
In writable and !referenced case, the result value should be
SCAN_LACK_REFERENCED_PAGE for trace_mm_collapse_huge_page_isolate()
instead of default 0 (SCAN_FAIL) here.
Fixes: 7d2eba0557c1 ("mm: add tracepoint for scanning pages")
Signed-off-by: Miaohe Lin
Acked-by: Kirill A. Shutemov
---
smp_wmb() is needed to avoid the copy_huge_page writes to become visible
after the set_pmd_at() write here. But we can reuse the smp_wmb() inside
__SetPageUptodate() to remove this redundant one.
Signed-off-by: Miaohe Lin
Acked-by: Kirill A. Shutemov
---
mm/khugepaged.c | 13 ++---
1
Commit 4d45e75a9955 ("mm: remove the now-unnecessary mmget_still_valid()
hack") have made khugepaged_test_exit() suitable for check mm->mm_users
against 0. Use this helper here.
Signed-off-by: Miaohe Lin
Acked-by: Kirill A. Shutemov
---
mm/khugepaged.c | 2 +-
1 file changed, 1 insertion(+), 1
Hi all,
This series contains cleanups to remove unneeded return value, use
helper function and so on. And there is one fix to correct the wrong
result value for trace_mm_collapse_huge_page_isolate().
More details can be found in the respective changelogs. Thanks!
v1->v2:
drop patch
The return value of khugepaged_collapse_pte_mapped_thps() is never checked
since it's introduced. We should remove such unneeded return value.
Signed-off-by: Miaohe Lin
Acked-by: Kirill A. Shutemov
---
mm/khugepaged.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git
On Fri, Mar 05, 2021 at 01:20:19PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.21 release.
> There are 102 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On 03/06/2021 11:06 AM, Huacai Chen wrote:
Hi, Qing,
On Sat, Mar 6, 2021 at 10:36 AM Qing Zhang wrote:
Add IO interrupt controller support for Loongson 2k1000, different
from the 3a series is that 2K1000 has 64 interrupt sources, 0-31
correspond to the device tree liointc0 device node, and
On Fri, Mar 05, 2021 at 01:21:02PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.4.103 release.
> There are 72 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Fri, Mar 05, 2021 at 07:43:54PM +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Use acpi_evaluation_failure_warn() introduced previously instead of
> the ACPICA-specific ACPI_EXCEPTION() macro to log warning messages
> regarding ACPI object evaluation failures and use dev_err()
On Fri, Mar 05, 2021 at 03:52:58AM -0600, Gustavo A. R. Silva wrote:
> In preparation to enable -Wimplicit-fallthrough for Clang, fix a warning
> by explicitly adding a break statement instead of letting the code fall
> through to the next case.
>
> Link: https://github.com/KSPP/linux/issues/115
On 03/05/2021 10:32 AM, Jiaxun Yang wrote:
在 2021/3/4 下午7:00, Qing Zhang 写道:
We don't need them anymore, They are uniform on all Loongson64 systems
and have been fixed in DeviceTree.loongson3_platform_init is replaced
with DTS + driver.
Signed-off-by: Jiaxun Yang
Signed-off-by: Qing
On 2021/3/6 1:38, Kirill A. Shutemov wrote:
> On Thu, Mar 04, 2021 at 07:30:12AM -0500, Miaohe Lin wrote:
>> Since commit 7ae88534cdd9 ("mm: move mem_cgroup_uncharge out of
>> __page_cache_release()"), the mem_cgroup will be uncharged when hpage is
>> freed. Uncharge mem_cgroup here is harmless
Replace the use of C bit-fields in the rmnet_map_dl_csum_trailer
structure with a single one-byte field, using constant field masks
to encode or get at embedded values.
Signed-off-by: Alex Elder
Reviewed-by: Bjorn Andersson
---
.../ethernet/qualcomm/rmnet/rmnet_map_data.c| 2 +-
The actual layout of bits defined in C bit-fields (e.g. int foo : 3)
is implementation-defined. Structures defined in
address this by specifying all bit-fields twice, to cover two
possible layouts.
I think this pattern is repetitive and noisy, and I find the whole
notion of compiler "bitfield
The following macros, defined in "rmnet_map.h", assume a socket
buffer is provided as an argument without any real indication this
is the case.
RMNET_MAP_GET_MUX_ID()
RMNET_MAP_GET_CD_BIT()
RMNET_MAP_GET_PAD()
RMNET_MAP_GET_CMD_START()
RMNET_MAP_GET_LENGTH()
What they hide is
Replace the use of C bit-fields in the rmnet_map_ul_csum_header
structure with a single two-byte (big endian) structure member,
and use field masks to encode or get values within it.
Previously rmnet_map_ipv4_ul_csum_header() would update values in
the host byte-order fields, and then forcibly
In rmnet_map_ipv4_ul_csum_header() and rmnet_map_ipv6_ul_csum_header()
the offset within a packet at which checksumming should commence is
calculated. This calculation involves byte swapping and a forced type
conversion that makes it hard to understand.
Simplify this by computing the offset in
Version 2 of this series fixes the code in the final patch that
encoded the RMNet checksum offload header inserted for outgoing
packets. It was erroneously using be16_encode_bits() to generate
the value to be written into the header, where it should have been
using u16_encode_bits(). Bjorn
The fields in the checksum trailer structure used for QMAP protocol
RX packets are all big-endian format, so define them that way.
It turns out these fields are never actually used by the RMNet code.
The start offset is always assumed to be zero, and the length is
taken from the other packet
On 03/05/2021 06:01 PM, Philippe Mathieu-Daudé wrote:
Hi,
On Thu, Mar 4, 2021 at 5:35 PM Qing Zhang wrote:
The purpose of separating loongson_system_configuration from boot_param.h
is to keep the other structure consistent with the firmware.
This is supposed to be a trivial patch, but the
Hi, Qing,
On Sat, Mar 6, 2021 at 10:36 AM Qing Zhang wrote:
>
> Add IO interrupt controller support for Loongson 2k1000, different
> from the 3a series is that 2K1000 has 64 interrupt sources, 0-31
> correspond to the device tree liointc0 device node, and the other
> correspond to liointc1 node.
Hi Arnaldo,
On Fri, Mar 05, 2021 at 02:29:44PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Feb 09, 2021 at 09:58:55AM +0800, Leo Yan escreveu:
> > On Mon, Feb 08, 2021 at 01:46:41PM -0700, Mathieu Poirier wrote:
> > > On Sat, Feb 06, 2021 at 11:08:29PM +0800, Leo Yan wrote:
> > > > From:
On 3/4/2021 7:35 AM, Adrian Hunter wrote:
On 3/03/21 12:52 am, Asutosh Das wrote:
During runtime-suspend of ufs host, the scsi devices are
already suspended and so are the queues associated with them.
But the ufs host sends SSU to wlun during its runtime-suspend.
During the process
On Fri, Mar 5, 2021 at 7:20 AM John Garry wrote:
>
> It has been reported many times that a use-after-free can be intermittently
> found when iterating busy requests:
>
> -
> https://lore.kernel.org/linux-block/8376443a-ec1b-0cef-8244-ed584b96f...@huawei.com/
> -
>
On Sat, Mar 06, 2021 at 11:18:31AM +0900, Masahiro Yamada wrote:
> On Sat, Mar 6, 2021 at 10:28 AM Josh Poimboeuf wrote:
> >
> > On Thu, Mar 04, 2021 at 08:25:00PM -0600, Josh Poimboeuf wrote:
> > > On Thu, Mar 04, 2021 at 03:37:14PM -0800, Linus Torvalds wrote:
> > > > On Thu, Mar 4, 2021 at
On 2021/3/6 1:40, Kirill A. Shutemov wrote:
> On Thu, Mar 04, 2021 at 07:30:08AM -0500, Miaohe Lin wrote:
>> Hi all,
>> This series contains cleanups to remove unneeded return value, use
>> helper function and so on. And there is one fix to correct the wrong
>> result value for
In bch_cached_dev_run(), free(env[1])|free(env[2])|free(buf)
show up three times. This patch introduce out tag in
which free(env[1])|free(env[2])|free(buf) are only called
one time. If we need to call free() when errors occur,
we can set error code to ret, and then goto out tag directly.
Add default config for 2K1000.
Signed-off-by: Jiaxun Yang
Signed-off-by: Qing Zhang
---
v2-v3: No change
arch/mips/configs/loongson2k_defconfig | 353 +
1 file changed, 353 insertions(+)
create mode 100644 arch/mips/configs/loongson2k_defconfig
diff --git
Distinguish between 3A series CPU and 2K1000 CPU UART0.
Signed-off-by: Jiaxun Yang
Signed-off-by: Qing Zhang
---
v2-v3: No change
arch/mips/loongson64/init.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/mips/loongson64/init.c b/arch/mips/loongson64/init.c
Get the fixed-clock from the CPU0 node of the device tree.
Signed-off-by: Jiaxun Yang
Signed-off-by: Qing Zhang
---
v2-v3: Add error process
arch/mips/loongson64/time.c | 20
1 file changed, 20 insertions(+)
diff --git a/arch/mips/loongson64/time.c
Add IO interrupt controller support for Loongson 2k1000, different
from the 3a series is that 2K1000 has 64 interrupt sources, 0-31
correspond to the device tree liointc0 device node, and the other
correspond to liointc1 node.
Signed-off-by: Jiaxun Yang
Signed-off-by: Qing Zhang
---
v2-v3: No
Add liointc-2.0 properties support, so update the maxItems and description.
Signed-off-by: Jiaxun Yang
Signed-off-by: Qing Zhang
---
v2-v3: Fix warnings/errors abount running 'make dt_binding_check'
.../bindings/interrupt-controller/loongson,liointc.yaml| 7 ---
1 file changed, 4
Add DTB boot support, only support LS2K1000 processor for now,
determine whether to use the built-in DTB or the DTB from the
firmware by checking the range of CKSEG0 and XKPHYS.loongson_fw
_interface will be used in the future.
Signed-off-by: Jiaxun Yang
Signed-off-by: Qing Zhang
---
v2-v3: No
These patches support single-core DTS boot to the serial port login
interface, which can be operated using conventional commands.
I have successfully tested it on the Loongson 2K1000 machine.
pmon: http://cgit.loongnix.org/cgit/pmon-loongson3/
Qing Zhang (7):
MIPS: Loongson64: DeviceTree for
Add DeviceTree files for Loongson 2K1000 processor,currently only
supports single-core boot.
Signed-off-by: Jiaxun Yang
Signed-off-by: Qing Zhang
---
v2-v3: No changes
arch/mips/boot/dts/loongson/Makefile | 1 +
.../boot/dts/loongson/loongson64-2k1000.dtsi | 243
On Fri, 5 Mar 2021 2:55 PM -0800 Jakub Kicinski wrote:
> On Fri, 5 Mar 2021 11:07:08 -0800 Don Bollinger wrote:
> > Acknowledging your objections, I nonetheless request that optoe be
> > accepted into upstream as an eeprom driver in drivers/misc/eeprom. It
> > is a legitimate driver, with a
These patches support single-core DTS boot to the serial port login
interface, which can be operated using conventional commands.
I have successfully tested it on the Loongson 2K1000 machine.
pmon: http://cgit.loongnix.org/cgit/pmon-loongson3/
Qing Zhang (7):
MIPS: Loongson64: DeviceTree for
The zram driver makes use of cpu hotplug multistate support,
whereby it associates a zram compression stream per CPU. To
support CPU hotplug multistate a callback enabled to allow
the driver to do what it needs when a CPU hotplugs.
It is however currently possible to end up removing the
zram
LTP's zram02.sh script can be used to crah your kernel pretty badly.
cd testcases/kernel/device-drivers/zram
while true; do PATH=$PATH:$PWD:$PWD/../../../lib/ ./zram02.sh; done
This won't do much, however if you run this in two separate windows
you'll see the kernel become unhappy quite
When we have sysfs attributes which muck with the driver
heavily we me end up with situations where the core
kernel driver removal call races with usage of a sysfs
attribute. The can happen when for instance a lock is
used on the sysfs attribute which is also used for
driver removal.
To fix this
On Sat, Mar 6, 2021 at 10:28 AM Josh Poimboeuf wrote:
>
> On Thu, Mar 04, 2021 at 08:25:00PM -0600, Josh Poimboeuf wrote:
> > On Thu, Mar 04, 2021 at 03:37:14PM -0800, Linus Torvalds wrote:
> > > On Thu, Mar 4, 2021 at 3:20 PM Kees Cook wrote:
> > > >
> > > > This seems fine to me, but I want to
Enable the Qualcomm SM8350 TLMM pinctrl and GCC clock drivers. They need
to be builtin to ensure that the UART is allowed to probe before user
space needs a console.
Signed-off-by: Bjorn Andersson
---
arch/arm64/configs/defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git
Add initial DTS for the Snapdragon 888 Mobile Hardware Development Kit,
aka SM8350 HDK. This initial version describes debug UART, UFS storage,
the three USB connectors and remoteprocs.
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/Makefile | 1 +
Define sev_enabled and sev_es_enabled as 'false' and explicitly #ifdef
out all of sev_hardware_setup() if CONFIG_KVM_AMD_SEV=n. This kills
three birds at once:
- Makes sev_enabled and sev_es_enabled off by default if
CONFIG_KVM_AMD_SEV=n. Previously, they could be on by default if
--
Hello,
I have a client with Assets in excess of $20B.He is ready to provide up to
$2B plus or minus for project funding on loan basis to any interested Party
whose project must not be sited in prohibited Countries and prohibited
businesses.We do not sponsor projects or enter into partnership,
Skip SEV's expensive WBINVD and DF_FLUSH if there are no SEV ASIDs
waiting to be reclaimed, e.g. if SEV was never used. This "fixes" an
issue where the DF_FLUSH fails during hardware teardown if the original
SEV_INIT failed. Ideally, SEV wouldn't be marked as enabled in KVM if
SEV_INIT fails,
Rename sev and sev_es to sev_enabled and sev_es_enabled respectively to
better align with other KVM terminology, and to avoid pseudo-shadowing
when the variables are moved to sev.c in a future patch ('sev' is often
used for local struct kvm_sev_info pointers).
No functional change intended.
Enable the 'sev' and 'sev_es' module params by default instead of having
them conditioned on CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT. The extra
Kconfig is pointless as KVM SEV/SEV-ES support is already controlled via
CONFIG_KVM_AMD_SEV, and CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT has the
Remove the forward declaration of sev_flush_asids(), which is only a few
lines above the function itself.
No functional change intended.
Reviewed by: Tom Lendacky
Reviewed-by: Brijesh Singh
Signed-off-by: Sean Christopherson
---
arch/x86/kvm/svm/sev.c | 1 -
1 file changed, 1 deletion(-)
Move the allocation of the SEV VMCB array to sev.c to help pave the way
toward encapsulating SEV enabling wholly within sev.c.
No functional change intended.
Reviewed by: Tom Lendacky
Reviewed-by: Brijesh Singh
Signed-off-by: Sean Christopherson
---
arch/x86/kvm/svm/sev.c | 12
Replace calls to svm_sev_enabled() with direct checks on sev_enabled, or
in the case of svm_mem_enc_op, simply drop the call to svm_sev_enabled().
This effectively replaces checks against a valid max_sev_asid with checks
against sev_enabled. sev_enabled is forced off by sev_hardware_setup()
if
Remove the redundant svm_sev_enabled() check when calling
sev_hardware_teardown(), the teardown helper itself does the check.
Removing the check from svm.c will eventually allow dropping
svm_sev_enabled() entirely.
No functional change intended.
Reviewed by: Tom Lendacky
Reviewed-by: Brijesh
Free sev_asid_bitmap if the reclaim bitmap allocation fails, othwerise
KVM will unnecessarily keep the bitmap when SEV is not fully enabled.
Freeing the page is also necessary to avoid introducing a bug when a
future patch eliminates svm_sev_enabled() in favor of using the global
'sev' flag
1 - 100 of 1526 matches
Mail list logo
