Bug: 220644706
Test: make and find the private modules in dist.
Change-Id: I4866d6ade1d13c640d26974d0a0590cba602fde7

Bug: 220644706
Test: make and find the private modules in dist.
Change-Id: I20ce519c5bdea4db191aa20cf742efaebf326542

Bug: 220644706
Test: make and find the private modules in dist.
Change-Id: Ic563fe6d2bc85a0255c6bc1ab363ce83cdc51793

Bug: 220644706
Change-Id: I6eb8f7d50016def7275a35b3ca2d358f617a4181

Provide the kernel build config file for build server.

Bug: 220644706
Change-Id: Ib52f329fc7082de053fd37e20596d69c4dc7bfc0

Enable the following options to support go/bandwidth-limiting:
- CONFIG_NET_SCH_TBF
- CONFIG_NET_CLS_MATCHALL
- CONFIG_NET_ACT_POLICE
- CONFIG_NET_ACT_BPF

bug: 157552970
     181855645
Change-Id: I6c7609ca642858d1282c7ddd0e9b1583ff4f4165

PD#SWPL-80006
b/229652967

Problem:
move vp9 prob process to Tee

Solution:
add interfaces for vp9 prob process

refer to:
https://scgit.amlogic.com/#/c/166331/



Verify:
android t + S905Y2-U221

Change-Id: I24002c71e537bef189f2cbfda86c9b855f43a23f
Signed-off-by: Xiaohang Cui <xiaohang.cui@amlogic.com>

PD#SWPL-57099
b/228938762

Problem:
TvtsJankHostTestCases need keep too many fd

Solution:
support max 128 fd

Verify:
T3

Change-Id: I082d6252250614344130233f92baf3845c1048ba
Signed-off-by: jintao xu <jintao.xu@amlogic.com>

PD#SWPL-75722

Problem:
need skip this test to rm CONFIG_CHECKPOINT_RESTORE

Solution:
rm CONFIG_CHECKPOINT_RESTORE to test

Verify:
Verify local

Change-Id: Ia53d0c5b55ee17e7223c418ddc8d23dfb97dcf56
Signed-off-by: weifang.liu <weifang.liu@amlogic.com>

PD#SWPL-76989
Bug: 227141269

Problem:
enable ramoops ramoops

Solution:
enable ramoops ramoops

Verify:
adt3

Signed-off-by: pengzhao.liu <pengzhao.liu@amlogic.com>
Change-Id: I76b01359c048f9945ccfbde676c14d218510b17a

PD#SWPL-75717
b/225279764

Problem:
2 Testcases failed in the module "vts_fs_test"

Solution:
change data partition to userdata
move partition mount from dts to fstab

Verify:
S905Y2-U221

Change-Id: I4a530337ef8c4220b68b3b1a49860c89044b89f9
Signed-off-by: hao.qi <hao.qi@amlogic.com>

PD#SWPL-71742
Bug: 171572148

Problem:
Map the permission gating RTM_GETNEIGH/RTM_GETNEIGHTBL messages to a
new permission so that it can be distinguished from the other netlink
route permissions in selinux policy. The new permission is triggered by
a flag set in system images T and up.

Solution:
This change is intended to be backported to all kernels that a T system
image can run on top of.

Verify:
on adt3-t kernel

Test: ateddst NetworkInterfaceTest
Test: atest CtsSelinuxTargetSdkCurrentTestCases
Test: atest bionic-unit-tests-static
Test: On Cuttlefish, run combinations of:
    - Policy bit set or omitted (see https://r.android.com/1701847

)
    - This patch applied or omitted
    - App having nlmsg_readneigh permission or not
  Verify that only the combination of this patch + the policy bit being
  set + the app not having the nlmsg_readneigh permission prevents the
  app from sending RTM_GETNEIGH messages.

Change-Id: I4bcfce4decb34ea9388eeedfc4be67403de8a980
Signed-off-by: Bram Bonné <brambonne@google.com>

Signed-off-by: pengzhao.liu <pengzhao.liu@amlogic.com>
Change-Id: Ic9d51cebab8c195537d54a28a23a7e93f09ba0b3

PD#SWPL-75333
BUG=225139017

Problem:
KernelTest#TestRateLimitingSupport fail

Solution:
add related kernel config

Verify:
local

Change-Id: Id1ec210fbe5d927061a70675652523079934b522
Signed-off-by: weifang.liu <weifang.liu@amlogic.com>

* changes:
  VPP: VPP code style modify [1/1]
  vpp: coding style modify [1/1]
  vpp: coding style modify [2/6]

This reverts commit 830f673c.

Reason for revert: Merged wrong CL

Change-Id: I16d4614c52a41f48fb657db48caff92aa5bff419

PD#SWPL-63211

Problem:
short of dm_bow config

Solution:
enable dm_bow config

Verify:
local

Change-Id: I503d20b44651b91ab13449d51814c2b1b668d9d7
Signed-off-by: lele.liu <lele.liu@amlogic.com>

This reverts commit 8e0c3065.

Reason for revert: 
Reason for revert: a better formatted patch will be submitted later

Change-Id: Ieb7dfa4f0bcbec9a4e26904618575baf840741e7

PD#NONE

Problem:
vts_kernel_checkpoint_test fail

Solution:
add config checkpoint and DB_BOW

Verify:
adt3

Signed-off-by: Pengfei Zhao <pengfei.zhao@amlogic.com>
Change-Id: I62102ab3d2c37afbb40c7c7a3e4ca212d83fe7e3

Bug: 204318789
Change-Id: Ic4b1aeeeff4f864543236b297b5548be4b9a9eb9

PD#SWPL-58477

Problem:
VPP code style modify

Solution:
VPP code style modify

Verify:
t3

Signed-off-by: yao liu <yao.liu@amlogic.com>
Change-Id: Ifc5bd9222d48c24de435745e9379d8bfe3dede69

PD#SWPL-58477

Problem:
fix error in last commit eac4

Solution:
fix error

Verify:
ohm

Signed-off-by: yao liu <yao.liu@amlogic.com>
Change-Id: I57affad1484c29d29a84eedcf4bc27da6d5fecb3

PD#SWPL-58477

Problem:
coding style issue

Solution:
coding style modify and code clean up

Verify:
Newton

Signed-off-by: yao liu <yao.liu@amlogic.com>
Change-Id: I92d3d3ce091a21178b1bc0d3205716e70a3aa7a7

PD#SWPL-61729
BUG=203412562

Problem:
Release 52 MB of unused memory allocated in "ion-dev"

Solution:
Release 52 MB of unused memory allocated in "ion-dev"

Verify:
adt3-S

Signed-off-by: Liang Ji <liang.ji@amlogic.com>
Change-Id: I87a24212cbf5b6ffac39fff94d52c498b226bb65

PD#SWPL-61507
BUG=202208062

commit 17839856fd588f4ab6b789f482ed3ffd7c403e1f upstream.

Doing a "get_user_pages()" on a copy-on-write page for reading can be
ambiguous: the page can be COW'ed at any time afterwards, and the
direction of a COW event isn't defined.

Yes, whoever writes to it will generally do the COW, but if the thread
that did the get_user_pages() unmapped the page before the write (and
that could happen due to memory pressure in addition to any outright
action), the writer could also just take over the old page instead.

End result: the get_user_pages() call might result in a page pointer
that is no longer associated with the original VM, and is associated
with - and controlled by - another VM having taken it over instead.

So when doing a get_user_pages() on a COW mapping, the only really safe
thing to do would be to break the COW when getting the page, even when
only getting it for reading.

At the same time, some users simply don't even care.

For example, the perf code wants to look up the page not because it
cares about the page, but because the code simply wants to look up the
physical address of the access for informational purposes, and doesn't
really care about races when a page might be unmapped and remapped
elsewhere.

This adds logic to force a COW event by setting FOLL_WRITE on any
copy-on-write mapping when FOLL_GET (or FOLL_PIN) is used to get a page
pointer as a result.

The current semantics end up being:

 - __get_user_pages_fast(): no change. If you don't ask for a write,
   you won't break COW. You'd better know what you're doing.

 - get_user_pages_fast(): the fast-case "look it up in the page tables
   without anything getting mmap_sem" now refuses to follow a read-only
   page, since it might need COW breaking.  Which happens in the slow
   path - the fast path doesn't know if the memory might be COW or not.

 - get_user_pages() (including the slow-path fallback for gup_fast()):
   for a COW mapping, turn on FOLL_WRITE for FOLL_GET/FOLL_PIN, with
   very similar semantics to FOLL_FORCE.

If it turns out that we want finer granularity (ie "only break COW when
it might actually matter" - things like the zero page are special and
don't need to be broken) we might need to push these semantics deeper
into the lookup fault path.  So if people care enough, it's possible
that we might end up adding a new internal FOLL_BREAK_COW flag to go
with the internal FOLL_COW flag we already have for tracking "I had a
COW".

Alternatively, if it turns out that different callers might want to
explicitly control the forced COW break behavior, we might even want to
make such a flag visible to the users of get_user_pages() instead of
using the above default semantics.

But for now, this is mostly commentary on the issue (this commit message
being a lot bigger than the patch, and that patch in turn is almost all
comments), with that minimal "enable COW breaking early" logic using the
existing FOLL_WRITE behavior.

[ It might be worth noting that we've always had this ambiguity, and it
  could arguably be seen as a user-space issue.

  You only get private COW mappings that could break either way in
  situations where user space is doing cooperative things (ie fork()
  before an execve() etc), but it _is_ surprising and very subtle, and
  fork() is supposed to give you independent address spaces.

  So let's treat this as a kernel issue and make the semantics of
  get_user_pages() easier to understand. Note that obviously a true
  shared mapping will still get a page that can change under us, so this
  does _not_ mean that get_user_pages() somehow returns any "stable"
  page ]

[surenb: backport notes
	Replaced (gup_flags | FOLL_WRITE) with write=1 in gup_pgd_range.
	Removed FOLL_PIN usage in should_force_cow_break since it's missing in
	the earlier kernels.
        Since gup_pgd_range does not exist, made appropriate changes on
        the the gup_huge_pgd, gup_huge_pd and gup_pud_range calls]

Reported-by: Jann Horn <jannh@google.com>
Tested-by: Christoph Hellwig <hch@lst.de>
Acked-by: Oleg Nesterov <oleg@redhat.com>
Acked-by: Kirill Shutemov <kirill@shutemov.name>
Acked-by: Jan Kara <jack@suse.cz>
Cc: Andrea Arcangeli <aarcange@redhat.com>
Cc: Matthew Wilcox <willy@infradead.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
[surenb: backport to 4.9 kernel]
Signed-off-by: Suren Baghdasaryan <surenb@google.com>

Signed-off-by: yao zhang1 <yao.zhang1@amlogic.com>
Change-Id: I877999f7b789aee6078ccade2ae54b827d88368f

PD#SWPL-54808
BUG=197895076

Problem:
CtsMediaTestCases 44 DecodeAccuracyTest cases failed

Solution:
add extend column and row for special resolution cts
add dump yuv data interface
add debug flag for cts workaround

Verify:
adt3

Change-Id: Ie461422fddab008d4d905930f5f40a612bb1a98b
Signed-off-by: binqi zhang <binqi.zhang@amlogic.com>
Signed-off-by: Pengfei Zhao <pengfei.zhao@amlogic.com>

SWPL-59636

Problem:
cma shrinker is not standard implement, which may cause
app being unexpected killed

Solution:
use lmkd to kill app.
disable cma shrinker

Signed-off-by: Shuide Chen <shuide.chen@amlogic.com>
Change-Id: I9e510f837047fdb2c8617efb3ba403c69d8f1b9c

* changes:
  ionvideo: support no drop i for cts [1/1]
  v4lvideo: set field V4L2_FIELD_INTERLACED when video is interlace [1/2]

PD#SWPL-54823

Problem:
ionvideo drop i cause cts fail

Solution:
ionvideo not drop i

Verify:
U221

Change-Id: Icbfcb56b69a657a43aaee26428568a5140836167
Signed-off-by: jintao xu <jintao.xu@amlogic.com>

PD#SWPL-32080

Problem:
omx need know interlace or not

Solution:
v4lvideo sent interlace info to omx

Verify:
AH212

Change-Id: I4ce4c5e8aeafe5ed920855cc5e1f3f2245eec9ce
Signed-off-by: jintao xu <jintao.xu@amlogic.com>

debug_fs should be disable in release build and pass XTS

Change-Id: Ica01a743a9ad64dab3c79ff00edea5d92202fd8e

PD#SWPL-57172

Problem:
hal can't receive suspend/resume uevent
on android S + 4.9-q

Solution:
add extra uevents to supplement extcon;
on android S, it will only listen to uevent
on android Q, it will only listen to extcon

Verify:
u221

Change-Id: I52fbe9756a824d6876753ae3ff36c7bb7b9b6f97
Signed-off-by: hang cheng <hang.cheng@amlogic.com>

PD#SWPL-49008

Problem:
hdmi early suspend uevent is not received by sysctl

Solution:
correct hdmipwr uevent init state

Verify:
AC214

Change-Id: I91f4e1643a58d54a8d0ca0f8cf50bd9ab6e1bd13
Signed-off-by: hang cheng <hang.cheng@amlogic.com>

PD#SWPL-56597

Problem:
Current the hdmi resume power uevent is early and before reading
edid, and this will make application can't get sink capability and
set the 480p as default

Solution:
Adjust the hdmi resume power uevent after reading edid

Verify:
g12/u212

Change-Id: I20acd118762d167ccfbf790c8fbace3171b0fda3
Signed-off-by: Zongdong Jiao <zongdong.jiao@amlogic.com>

PD#SWPL-55323

Problem:
the hdmi_pwr is too late in resume

Solution:
head the hdmi_pwr in resume

Verify:
G12/U212

Change-Id: I86bd4dfd0c6b51578cb09fd4fc8902b858de9eae
Signed-off-by: Zongdong Jiao <zongdong.jiao@amlogic.com>