[Kernel-packages] [Bug 1834423] Re: Enable intel_rapl on Idaville

[quanxian]

Patch shipped in 5.3-rc1
3231a21d5ca6f6baea95588406775304f35a203e

** Changed in: intel
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1834423

Title:
  Enable intel_rapl on Idaville

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:
  Validate and enable RAPL on Idaville /ICX -D.

  Target Kernel: 5.3
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1834423/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1771252] Re: [ICL] Enable intel_rapl driver for Icelake

[quanxian]

Patch for ICLLAKE MOBILE intel_rapl support shipped in 5.3-rc1.

0ab74bcd1b50821391b264150d26b7f03ba6740b
ba6f3ec198d555d0c9b7e038cb003922aea2797d

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771252

Title:
  [ICL] Enable intel_rapl driver for Icelake

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released

Bug description:
  Desription:
  This feature is intended to track intel_rapl driver enabling for IceLake.

  Commit:Powercap/intel_rapl driver enabling for Icelake

  Target Release: 19.10
  Target Kernel: 5.1

  SRU Justification
  [Impact]
  New CPU is required to be listed in Intel RAPL (Running Average Power Limit) 
driver.

  [Fix]
  From Intel's suggestion, below 2 commits are required
 ba6f3ec198d5 powercap/intel_rapl: add Ice Lake mobile
 df7f8e00a50f powercap: intel_rapl: add support for Jacobsville

  [Test]
  Boot up Intel ICL-Y SDP with the patched kernel, nothing abnormal, but I'm 
unable to distinguish the difference.

  [Regression Potential]
  Low, the 2 commits add new ID to the table, should affect new CPU only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1771252/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1834421] Re: perf enable core PMU counters for Idaville

[quanxian]

faaeff98666c24376cebd0b106504d05a36881d1
5.3-rc1

** Changed in: intel
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1834421

Title:
  perf enable core PMU counters for Idaville

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:

  Enable Ice Lake -D server core PMU counters.

  Target Kernel: 5.3
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1834421/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1834413] Re: SNR: perf enable uncore PMU counters

[quanxian]

07ce734dd8adc0f170d43c15a9b91b707a21b9d7
210cc5f9db7a5c66b7ca6290b7d35cc7db7e9dbd
3da04b8a00dd6d39970b9e764b78c5dfb40ec013
c8872d90e0a3651a096860d3241625ccfa1647e0
ee49532b38dd084650bf715eabe7e3828fb8d275

5.3-rc1

** Changed in: intel
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1834413

Title:
  SNR: perf enable uncore PMU counters

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:

  perf enable uncore PMU counters for Jacobsville

  Target Kernel: 5.3

  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1834413/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1782206] Re: KVM enable SnowRidge Accelerator Interfacing Architecture (AIA)

[quanxian]

** Description changed:

  CPU core (Tremont) includes Accelerator Interfacing Architecture (AIA) 
features including:
  - UMONITOR/UMWAIT: Ring-3 MONITOR/MWAIT with timeout. For memory-based synch 
with accelerators
  - TPAUSE: Monitor-less wait (with timeout). For wait-on-multiple or 
wait-for-interrupt usages
  - MOVDIRI: 8B streaming doorbell write capability. For streaming accelerator 
usages.
  - MOVDIR64B: Non-temporal write with 64B guaranteed write-atomicity. For 
latency critical accelerator usages
  
- Upstream target linux 5.3/Qemu-3.10
+ Upstream target linux 5.4/Qemu-3.10
  
  Target Release: 19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1782206

Title:
  KVM enable SnowRidge Accelerator Interfacing Architecture (AIA)

Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Fix Released
Status in xen package in Ubuntu:
  Incomplete

Bug description:
  CPU core (Tremont) includes Accelerator Interfacing Architecture (AIA) 
features including:
  - UMONITOR/UMWAIT: Ring-3 MONITOR/MWAIT with timeout. For memory-based synch 
with accelerators
  - TPAUSE: Monitor-less wait (with timeout). For wait-on-multiple or 
wait-for-interrupt usages
  - MOVDIRI: 8B streaming doorbell write capability. For streaming accelerator 
usages.
  - MOVDIR64B: Non-temporal write with 64B guaranteed write-atomicity. For 
latency critical accelerator usages

  Upstream target linux 5.4/Qemu-3.10

  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782206/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1834417] Re: EDAC driver support for Idaville

[quanxian]

1dc78f1ffa3a386b986b659884952d816021f38f
5c5d3ac2064ae2466c81d40186bcc09b2d5b7892
c4a1dd9e83ceceef6ffba82b8b274ab9b929ea14 
5.3-rc1

** Changed in: intel
   Status: New => Fix Committed

** Description changed:

  Description:
  Provide detailed memory topology and configuration information as well as 
translating error addresses to physical DIMM addresses.
  
  Target Release: 19.10
- Target Kernel:5.2
+ Target Kernel:5.3

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1834417

Title:
  EDAC driver support for Idaville

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:
  Provide detailed memory topology and configuration information as well as 
translating error addresses to physical DIMM addresses.

  Target Release: 19.10
  Target Kernel:5.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1834417/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1837675] [NEW] Implement RAPL control via Processor device MMIO

[quanxian]

Public bug reported:

Description:

Implement RAPL control via MMIO so that thermald can take advantage of
it.


0c2ddedd8bcb88c4100acb9e0fc5ac8752d09501 
1193b1658d16f03cdb2edbac5f2a796ccca225af 
3382388d714891fc0f575926189f33d22e7c960b 
7ebf8eff63b4f349e7b2ded6aa5036d94bdf94b9 
7fde2712a7adab721eaabafbd8ff93dff3262d35 
8310e8202f24d674b6b2bd341af15d72299f696d 
8a00676cd690941c9a18bd390c3b2cade631c516 
abcfaeb3f5dc8bded4ba446eb2fb017a7a41d9bc 
beea8df821d928e7755917da6c1e45d6afde5148 
d978e755aabe215cb67bf713e103ed3916ec306d 
f7c4e0c89bbd0f008b33d9dce02e207d9dea9f54 
ff956826a403f5cf189978d5ff6b3eb53aa11610 

Still have two patches which will be shipped in 5.3-rc2 and will update
the commit ids then.

Target Kernel: 5.3
Target Release: 19.10

** Affects: intel
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: eoan intel-kernel-19.10

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1837675

Title:
  Implement RAPL control via Processor device MMIO

Status in intel:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:

  Implement RAPL control via MMIO so that thermald can take advantage of
  it.

  
  0c2ddedd8bcb88c4100acb9e0fc5ac8752d09501 
1193b1658d16f03cdb2edbac5f2a796ccca225af 
3382388d714891fc0f575926189f33d22e7c960b 
7ebf8eff63b4f349e7b2ded6aa5036d94bdf94b9 
7fde2712a7adab721eaabafbd8ff93dff3262d35 
8310e8202f24d674b6b2bd341af15d72299f696d 
8a00676cd690941c9a18bd390c3b2cade631c516 
abcfaeb3f5dc8bded4ba446eb2fb017a7a41d9bc 
beea8df821d928e7755917da6c1e45d6afde5148 
d978e755aabe215cb67bf713e103ed3916ec306d 
f7c4e0c89bbd0f008b33d9dce02e207d9dea9f54 
ff956826a403f5cf189978d5ff6b3eb53aa11610 

  Still have two patches which will be shipped in 5.3-rc2 and will
  update the commit ids then.

  Target Kernel: 5.3
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1837675/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1824922] Re: [Graphics] CometLake graphics support

[quanxian]

** Changed in: intel
   Status: New => Incomplete

** Changed in: intel
   Status: Incomplete => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1824922

Title:
  [Graphics] CometLake graphics support

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:

  a new PCIID is added to support CometLake graphics. Please add it into
  19.04 if possible.

  commit 729ae330a0f2e270db2ca70c06a83d0aa2776288

  Target Release: 19.04
  Target Kernel: 5.1-rc6

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1824922/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1824922] Re: [Graphics] CometLake graphics support

[quanxian]

** Changed in: intel
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1824922

Title:
  [Graphics] CometLake graphics support

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:

  a new PCIID is added to support CometLake graphics. Please add it into
  19.04 if possible.

  commit 729ae330a0f2e270db2ca70c06a83d0aa2776288

  Target Release: 19.04
  Target Kernel: 5.1-rc6

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1824922/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1834119] Re: [AEP-BUG] Critical:concurrent invocations of ndctl can cause linux panic

[quanxian]

87a30e1f05d7 driver-core, libnvdimm: Let device subsystems add local lockdep 
coverage
ca6bf264f6d8 libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
b70d31d054ee libnvdimm/bus: Stop holding nvdimm_bus_list_mutex over __nd_ioctl()
6de5d06e657a libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
700cd033a82d libnvdimm/region: Register badblocks before namespaces
8aac0e233891 libnvdimm/bus: Prevent duplicate device_unregister() calls

** Description changed:

  Description:
  
  Patch: fix patch in the libnvdimm pending tree.
  Proposed fixes here: 
https://lists.01.org/pipermail/linux-nvdimm/2019-June/021847.html
  and pushed out to libnvdimm-pending: 
https://git.kernel.org/pub/scm/linux/kernel/git/djbw/nvdimm.git/log/?h=libnvdimm-pending
- 
  
  Upstream Bug link: https://github.com/pmem/ndctl/issues/96
  
  The problem is fairly easy to reproduce in as little as 10 minutes.
  Do the following in parallel, like in separate terminals. Example...
  in term #1, #3, #5, type
  while [1]; do ndctl create-namespace -m devdax -s 48G done
  in term #2, #4, #6, type
  while [1]; do ndctl destroy-namespace all -f done
  
  Even simple invocation will eventually lead to a panic, it can take hours 
though. Example...
  in term #1 run the script
  #/bin/bash
  while /bin/true
  do
  ndctl destroy-namespace -f all
  date
  for R in ndctl list -R | jq -r ".[] | .dev"
  do
  for i in {1..10}
  do
  ndctl create-namespace -r $R -s 8g -m devdax
  done
  done
  done
  in term #2 type
  while /bin/true; do ndctl list done
  
  Run that same terminal #1 script in 2 separate terminals, thereby
  creating 2 separate threads that will destroy/create will usually result
  in a panic within an hour.
  
- Target Kernel: 5.2
+ Target Kernel: 5.3
  Target Release: 19.10

** Changed in: intel
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1834119

Title:
  [AEP-BUG] Critical:concurrent invocations of ndctl can cause linux
  panic

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:

  Patch: fix patch in the libnvdimm pending tree.
  Proposed fixes here: 
https://lists.01.org/pipermail/linux-nvdimm/2019-June/021847.html
  and pushed out to libnvdimm-pending: 
https://git.kernel.org/pub/scm/linux/kernel/git/djbw/nvdimm.git/log/?h=libnvdimm-pending

  Upstream Bug link: https://github.com/pmem/ndctl/issues/96

  The problem is fairly easy to reproduce in as little as 10 minutes.
  Do the following in parallel, like in separate terminals. Example...
  in term #1, #3, #5, type
  while [1]; do ndctl create-namespace -m devdax -s 48G done
  in term #2, #4, #6, type
  while [1]; do ndctl destroy-namespace all -f done

  Even simple invocation will eventually lead to a panic, it can take hours 
though. Example...
  in term #1 run the script
  #/bin/bash
  while /bin/true
  do
  ndctl destroy-namespace -f all
  date
  for R in ndctl list -R | jq -r ".[] | .dev"
  do
  for i in {1..10}
  do
  ndctl create-namespace -r $R -s 8g -m devdax
  done
  done
  done
  in term #2 type
  while /bin/true; do ndctl list done

  Run that same terminal #1 script in 2 separate terminals, thereby
  creating 2 separate threads that will destroy/create will usually
  result in a panic within an hour.

  Target Kernel: 5.3
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1834119/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1835350] Re: Hang / zombie process from Xarray page-fault conversion

[quanxian]

d75996dd022b dax: dax_layout_busy_page() should not unmap cow pages
61c30c98ef17 dax: Fix missed wakeup in put_unlocked_entry()

** Changed in: intel
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1835350

Title:
  Hang / zombie process from Xarray page-fault conversion

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:

  We're seeing a case where RocksDB hangs and becomes defunct when
  trying to kill the process. v4.19 succeeds and v4.20 fails. Robert was
  able to bisect this to commit b15cd800682f "dax: Convert page fault
  handlers to XArray".

  Target Release: 19.10
  Target Kernel: 5.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1835350/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801219] Re: [SKL]Export XSAVE AVX state in /proc/pid

[quanxian]

0c608dad2a771c0a11b6d12148d1a8b975e015d4
2f7726f955572e587d5f50fbe9b2deed5334bd90
68bc30bb9f33fc8d11e3d110d29e06490896a999
711486fd18596315d42cebaac3dba8c408f60a3d

v5.3

** Changed in: intel
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801219

Title:
  [SKL]Export XSAVE AVX state in /proc/pid

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description
  There is some interest to separate AVX512 using processes from non AVX 
processes to get higher frequency.

  A user space tool doing this needs to know whether AVX is used. One way would 
be to export the information from the XSAVE state from the last context switch 
in /proc/pid/*
  Should report if AVX or AVX512 state is non INIT.

  Target Kernel: 5.2
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801219/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

[quanxian]

Commit:2bdb76c015df7125783d8394d6339d181cb5bc30

git tag --contains 2bdb76c015df7125783d8394d6339d181cb5bc30
v5.1
v5.1-rc3
v5.1-rc4
v5.1-rc5
v5.1-rc6
v5.1-rc7


** Description changed:

  This is a bug.
  
  Test Environment:
  
  Repro Steps:
  
  1. Boot up guest using: -cpu Cascadelake-Server
  
  [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive
  if=virtio,id=hd,file=/home/yexin/rhel7u6.qcow2,format=qcow2  -m 4096
  -smp 4 -cpu Cascadelake-Server -serial stdio
  
  char device redirected to /dev/pts/3 (label serial0)
  
  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]
  
  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]
  
  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]
  
  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]
  
  2. To check CPU ID related to features[FEAT_7_0_EDX]
  ：CPUID_7_0_EDX_ARCH_CAPABILITIES
  
  Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1.
  
  Actual Result:
  
  Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b
  ecx=0x0818 edx=0xbc00  (EDX bit 29=1)
  
  Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9
  ecx=0x0818 edx=0x8400 (EDX bit 29=0)
  
+ Commit:2bdb76c015df7125783d8394d6339d181cb5bc30
+ 
+ Target Kerned: 5.1
  Target Release: 19.10

** Description changed:

  This is a bug.
  
  Test Environment:
  
  Repro Steps:
  
  1. Boot up guest using: -cpu Cascadelake-Server
  
  [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive
- if=virtio,id=hd,file=/home/yexin/rhel7u6.qcow2,format=qcow2  -m 4096
- -smp 4 -cpu Cascadelake-Server -serial stdio
+ if=virtio,id=hd,file=/home/x/x,format=qcow2  -m 4096 -smp 4 -cpu
+ Cascadelake-Server -serial stdio
  
  char device redirected to /dev/pts/3 (label serial0)
  
  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]
  
  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]
  
  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]
  
  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]
  
  2. To check CPU ID related to features[FEAT_7_0_EDX]
  ：CPUID_7_0_EDX_ARCH_CAPABILITIES
  
  Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1.
  
  Actual Result:
  
  Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b
  ecx=0x0818 edx=0xbc00  (EDX bit 29=1)
  
  Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9
  ecx=0x0818 edx=0x8400 (EDX bit 29=0)
  
  Commit:2bdb76c015df7125783d8394d6339d181cb5bc30
  
  Target Kerned: 5.1
  Target Release: 19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1828495

Title:
  [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

Status in intel:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  This is a bug.

  Test Environment:

  Repro Steps:

  1. Boot up guest using: -cpu Cascadelake-Server

  [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive
  if=virtio,id=hd,file=/home/x/x,format=qcow2  -m 4096 -smp 4 -cpu
  Cascadelake-Server -serial stdio

  char device redirected to /dev/pts/3 (label serial0)

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  2. To check CPU ID related to features[FEAT_7_0_EDX]
  ：CPUID_7_0_EDX_ARCH_CAPABILITIES

  Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be
  1.

  Actual Result:

  Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b
  ecx=0x0818 edx=0xbc00  (EDX bit 29=1)

  Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9
  ecx=0x0818 edx=0x8400 (EDX bit 29=0)

  Commit:2bdb76c015df7125783d8394d6339d181cb5bc30

  Target Kerned: 5.1
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1828495] [NEW] [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

[quanxian]

Public bug reported:

This is a bug.

Test Environment:

Repro Steps:

1. Boot up guest using: -cpu Cascadelake-Server

[root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive
if=virtio,id=hd,file=/home/x/x,format=qcow2  -m 4096 -smp 4 -cpu
Cascadelake-Server -serial stdio

char device redirected to /dev/pts/3 (label serial0)

qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.07H:ECX [bit 4]

qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.07H:ECX [bit 4]

qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.07H:ECX [bit 4]

qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.07H:ECX [bit 4]

2. To check CPU ID related to features[FEAT_7_0_EDX]
：CPUID_7_0_EDX_ARCH_CAPABILITIES

Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1.

Actual Result:

Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b
ecx=0x0818 edx=0xbc00  (EDX bit 29=1)

Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9
ecx=0x0818 edx=0x8400 (EDX bit 29=0)

Commit:2bdb76c015df7125783d8394d6339d181cb5bc30

Target Kerned: 5.1
Target Release: 19.10

** Affects: intel
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: intel-kernel-19.10

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- 2.[KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
+ [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1828495

Title:
  [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

Status in intel:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  This is a bug.

  Test Environment:

  Repro Steps:

  1. Boot up guest using: -cpu Cascadelake-Server

  [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive
  if=virtio,id=hd,file=/home/x/x,format=qcow2  -m 4096 -smp 4 -cpu
  Cascadelake-Server -serial stdio

  char device redirected to /dev/pts/3 (label serial0)

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  2. To check CPU ID related to features[FEAT_7_0_EDX]
  ：CPUID_7_0_EDX_ARCH_CAPABILITIES

  Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be
  1.

  Actual Result:

  Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b
  ecx=0x0818 edx=0xbc00  (EDX bit 29=1)

  Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9
  ecx=0x0818 edx=0x8400 (EDX bit 29=0)

  Commit:2bdb76c015df7125783d8394d6339d181cb5bc30

  Target Kerned: 5.1
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1782212] Re: KVM CLX ACPI HMAT table support

[quanxian]

** Tags removed: intel-virt-19.04
** Tags added: intel-virt-19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1782212

Title:
  KVM CLX ACPI HMAT table support

Status in linux package in Ubuntu:
  Expired

Bug description:
  ACPI HMAT table support : HMAT is a new ACPI table that records the
  performance parameter of memory, so MCDRAM (or next gen HBM2) can be
  described well by this table. We need to support this table in kernel
  and qemu so that guest can get and parse this table then to find where
  the high-performance memory is.

  Heterogeneous Memory Attribute Table (HMAT) describes the memory attributes, 
such as memory
   side cache attributes and bandwidth and latency details, related to the 
System Physical Address
   (SPA) Memory Ranges. The software is expected to use this information as 
hint for optimization.

  HMAT is defined in ACPI 6.2: 5.2.27 Heterogeneous Memory Attribute Table 
(HMAT).
  http://www.uefi.org/sites/default/files/resources/ACPI_6_2.pdf
   patches:
  http://lists.nongnu.org/archive/html/qemu-devel/2018-06/msg05368.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782212/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801014] Re: perf tool needs to support per-die aggregation

[quanxian]

** Description changed:

  Description
  Add option "--per-die" to aggregate counts per physical die for CLX-AP and 
CPX.
  For previous platforms, "-per-die" equals to "-per-socket".
  
+ Target Kernel:5.3
  Target Release: 19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801014

Title:
  perf tool needs to support per-die aggregation

Status in intel:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description
  Add option "--per-die" to aggregate counts per physical die for CLX-AP and 
CPX.
  For previous platforms, "-per-die" equals to "-per-socket".

  Target Kernel:5.3
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801014/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1829689] Re: [AEP]Sub-section memory hotplug support, fix namepsace padding

[quanxian]

it is the continual bug of LP#1823595 (which is initial fix), more fixes
will be in this bug.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829689

Title:
  [AEP]Sub-section memory hotplug support, fix namepsace padding

Status in intel:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  The memory hotplug section is an arbitrary / convenient unit for memory
  hotplug. 'Section-size' units have bled into the user interface
  ('memblock' sysfs) and can not be changed without breaking existing
  userspace. The section-size constraint, while mostly benign for typical
  memory hotplug, has and continues to wreak havoc with 'device-memory'
  use cases, persistent memory (pmem) in particular. Recall that pmem uses
  devm_memremap_pages(), and subsequently arch_add_memory(), to allocate a
  'struct page' memmap for pmem. However, it does not use the 'bottom
  half' of memory hotplug, i.e. never marks pmem pages online and never
  exposes the userspace memblock interface for pmem. This leaves an
  opening to redress the section-size constraint.

  To date, the libnvdimm subsystem has attempted to inject padding to
  satisfy the internal constraints of arch_add_memory(). Beyond
  complicating the code, leading to bugs [2], wasting memory, and limiting
  configuration flexibility, the padding hack is broken when the platform
  changes this physical memory alignment of pmem from one boot to the
  next. Device failure (intermittent or permanent) and physical
  reconfiguration are events that can cause the platform firmware to
  change the physical placement of pmem on a subsequent boot, and device
  failure is an everyday event in a data-center.

  It turns out that sections are only a hard requirement of the
  user-facing interface for memory hotplug and with a bit more
  infrastructure sub-section arch_add_memory() support can be added for
  kernel internal usages like devm_memremap_pages(). Here is an analysis
  of the current design assumptions in the current code and how they are
  addressed in the new implementation:

  Current design assumptions:

  Sections that describe boot memory (early sections) are never
  unplugged / removed.
  pfn_valid(), in the CONFIG_SPARSEMEM_VMEMMAP=y, case devolves to a
  valid_section() check
  __add_pages() and helper routines assume all operations occur in
  PAGES_PER_SECTION units.
  The memblock sysfs interface only comprehends full sections
  New design assumptions:

  Sections are instrumented with a sub-section bitmask to track (on x86)
  individual 2MB sub-divisions of a 128MB section.
  Partially populated early sections can be extended with additional
  sub-sections, and those sub-sections can be removed with
  arch_remove_memory(). With this in place we no longer lose usable memory
  capacity to padding.
  pfn_valid() is updated to look deeper than valid_section() to also check the
  active-sub-section mask. This indication is in the same cacheline as
  the valid_section() so the performance impact is expected to be
  negligible. So far the lkp robot has not reported any regressions.
  Outside of the core vmemmap population routines which are replaced,
  other helper routines like shrink_{zone,pgdat}_span() are updated to
  handle the smaller granularity. Core memory hotplug routines that deal
  with online memory are not touched.

  The existing memblock sysfs user api guarantees / assumptions are
  not touched since this capability is limited to !online
  !memblock-sysfs-accessible sections.
  Meanwhile the issue reports continue to roll in from users that do not
  understand when and how the 128MB constraint will bite them. The current
  implementation relied on being able to support at least one misaligned
  namespace, but that immediately falls over on any moderately complex
  namespace creation attempt. Beyond the initial problem of 'System RAM'
  colliding with pmem, and the unsolvable problem of physical alignment
  changes, Linux is now being exposed to platforms that collide pmem
  ranges with other pmem ranges by default [3]. In short,
  devm_memremap_pages() has pushed the venerable section-size constraint
  past the breaking point, and the simplicity of section-aligned
  arch_add_memory() is no longer tenable.

  Target Kernel: 5.3
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1829689/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1829689] [NEW] [AEP]Sub-section memory hotplug support, fix namepsace padding

[quanxian]

Public bug reported:

The memory hotplug section is an arbitrary / convenient unit for memory
hotplug. 'Section-size' units have bled into the user interface
('memblock' sysfs) and can not be changed without breaking existing
userspace. The section-size constraint, while mostly benign for typical
memory hotplug, has and continues to wreak havoc with 'device-memory'
use cases, persistent memory (pmem) in particular. Recall that pmem uses
devm_memremap_pages(), and subsequently arch_add_memory(), to allocate a
'struct page' memmap for pmem. However, it does not use the 'bottom
half' of memory hotplug, i.e. never marks pmem pages online and never
exposes the userspace memblock interface for pmem. This leaves an
opening to redress the section-size constraint.

To date, the libnvdimm subsystem has attempted to inject padding to
satisfy the internal constraints of arch_add_memory(). Beyond
complicating the code, leading to bugs [2], wasting memory, and limiting
configuration flexibility, the padding hack is broken when the platform
changes this physical memory alignment of pmem from one boot to the
next. Device failure (intermittent or permanent) and physical
reconfiguration are events that can cause the platform firmware to
change the physical placement of pmem on a subsequent boot, and device
failure is an everyday event in a data-center.

It turns out that sections are only a hard requirement of the
user-facing interface for memory hotplug and with a bit more
infrastructure sub-section arch_add_memory() support can be added for
kernel internal usages like devm_memremap_pages(). Here is an analysis
of the current design assumptions in the current code and how they are
addressed in the new implementation:

Current design assumptions:

Sections that describe boot memory (early sections) are never
unplugged / removed.
pfn_valid(), in the CONFIG_SPARSEMEM_VMEMMAP=y, case devolves to a
valid_section() check
__add_pages() and helper routines assume all operations occur in
PAGES_PER_SECTION units.
The memblock sysfs interface only comprehends full sections
New design assumptions:

Sections are instrumented with a sub-section bitmask to track (on x86)
individual 2MB sub-divisions of a 128MB section.
Partially populated early sections can be extended with additional
sub-sections, and those sub-sections can be removed with
arch_remove_memory(). With this in place we no longer lose usable memory
capacity to padding.
pfn_valid() is updated to look deeper than valid_section() to also check the
active-sub-section mask. This indication is in the same cacheline as
the valid_section() so the performance impact is expected to be
negligible. So far the lkp robot has not reported any regressions.
Outside of the core vmemmap population routines which are replaced,
other helper routines like shrink_{zone,pgdat}_span() are updated to
handle the smaller granularity. Core memory hotplug routines that deal
with online memory are not touched.

The existing memblock sysfs user api guarantees / assumptions are
not touched since this capability is limited to !online
!memblock-sysfs-accessible sections.
Meanwhile the issue reports continue to roll in from users that do not
understand when and how the 128MB constraint will bite them. The current
implementation relied on being able to support at least one misaligned
namespace, but that immediately falls over on any moderately complex
namespace creation attempt. Beyond the initial problem of 'System RAM'
colliding with pmem, and the unsolvable problem of physical alignment
changes, Linux is now being exposed to platforms that collide pmem
ranges with other pmem ranges by default [3]. In short,
devm_memremap_pages() has pushed the venerable section-size constraint
past the breaking point, and the simplicity of section-aligned
arch_add_memory() is no longer tenable.

Target Kernel: 5.3
Target Release: 19.10

** Affects: intel
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: intel-kernel-19.10

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829689

Title:
  [AEP]Sub-section memory hotplug support, fix namepsace padding

Status in intel:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  The memory hotplug section is an arbitrary / convenient unit for memory
  hotplug. 'Section-size' units have bled into the user interface
  ('memblock' sysfs) and can not be changed without breaking existing
  userspace. The section-size constraint, while mostly benign for typical
  memory hotplug, has and continues to wreak havoc with 'device-memory'
  use cases, persistent memory (pmem) in particular. Recall that pmem uses
  devm_memremap_pages(), and subsequently arch_add_memory(), to allocate a
  'struct page' memmap for pmem.

[Kernel-packages] [Bug 1782209] Re: KVM SnowRidge Split-lock disable

[quanxian]

** Description changed:

  When bit 29 is set in Test Control MSR register 0x33, a #AC execption
   is generated for split locked accesses at all CPL irrespective of
   CR0.AM or EFLAGS.AC.
  
  This feature can help developers to capture memory accesses that across
  cachelines with #LOCK assertion. Then developers can reconstruct their
  program accordingly
  
- Upstream target linux 5.2
+ Upstream target linux 5.3
  Target Release: 19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1782209

Title:
  KVM SnowRidge Split-lock disable

Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  New

Bug description:
  When bit 29 is set in Test Control MSR register 0x33, a #AC execption
   is generated for split locked accesses at all CPL irrespective of
   CR0.AM or EFLAGS.AC.

  This feature can help developers to capture memory accesses that
  across cachelines with #LOCK assertion. Then developers can
  reconstruct their program accordingly

  Upstream target linux 5.3
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782209/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1819413] Re: [ICL] S0ix Enabling

[quanxian]

** Changed in: intel
   Status: Fix Committed => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1819413

Title:
  [ICL] S0ix Enabling

Status in intel:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux-oem-osp1 source package in Bionic:
  In Progress

Bug description:
  Description:

  S0ix-states represent the residency in the Intel® SoC idle standby power 
states.
  The S0ix states shut off part of the SoC when they are not in use. The S0ix
  states are triggered when specific conditions within the SoC have been 
achieved,
  for example: certain components are in low power states. The SoC consumes the
  least amount of power in the deepest (for example, S0i3) state.

  S0ix is triggered by two paths:
  (1) by system PM, e.g "suspend-to-idle" triggered by pressing the power button
  on Android device or command manually triggered on any Linux based distros;

  (2) by runtime PM, i.e no system activities with display off.

  S0ix should simply work in theory with trigger path (1) if we have the device
  drivers ready. On GLK, we require the below PCI device drivers with system PM
  support. ACPI device requirements are WIP.

   I2C designware PCI driver
   USB XHCI PCI ID
   Intel trace Hub[NPK) PCI ID
   SPI BXT PCI ID
   SCSI UFS BXT PCI host ID
   Graphics
   Audio
   PWM
   HSUART
   Security engine

  S0ix with trigger path (2) require work as defined below.
   All the above device drivers need to support runtime PM (already defined in 
the same LCK above)
   PCI root port to support runtime PM

  Both paths will require intel_idle driver support for S0ix support.

  238f9c11351f8af8534ae0318b4d9acc77b09ee8

  8aba056a4ea6da18186025a335a96b2f071e69d3

  6769fdbe27d782dfee5e459e25b44baacc7c8459

  cfb55af9add9c19806300fdb31f4cd25e67c6d1a

  4a5861f714293767980e4948c9a7c9e5e09c9b94

  2a13096ac7da07a1bfc9d91fc4a982020e7ded2b

  cd89e92b7399a69512b8d855a2dd145c47399bf8

  d6827015e671cd17871c9b7a0fabe06c044f7470

  0e68eeea9894feeba2edf7ec63e4551b87f39621

  e50af8332785355de3cb40d9f5e8c45dbfc86f53

  Target Kernel: 5.1
  Target Release: 19.10

  SRU Justification
  [Impact]
  Requires patches to make new INTEL CPU IceLake support s0ix
  [Fix]
  The patch list is provided by Intel
     238f9c11351f platform/x86: intel_pmc_core: Quirk to ignore XTAL
  shutdown
     8aba056a4ea6 platform/x86: intel_pmc_core: Add Package cstates residency 
info
     6769fdbe27d7 platform/x86: intel_pmc_core: Add ICL platform support
     cfb55af9add9 platform/x86: intel_pmc_core: Convert to INTEL_CPU_FAM6 macro
     4a5861f71429 platform/x86: intel_pmc_core: Avoid a u32 overflow
     2a13096ac7da platform/x86: intel_pmc_core: Include Reserved IP for LTR
     cd89e92b7399 platform/x86: intel_pmc_core: Fix file permissions for 
ltr_show
     d6827015e671 platform/x86: intel_pmc_core: Fix PCH IP name
     0e68eeea9894 platform/x86: intel_pmc_core: Fix PCH IP sts reading
     e50af8332785 platform/x86: intel_pmc_core: Handle CFL regmap properly

  Below commit fix 238f9c11351f ("platform/x86: intel_pmc_core: Quirk to ignore 
XTAL shutdown")
     9ae11e237d95 platform/x86: intel_pmc_core: Mark local function static

  [Test]
  Verified on Intel ICL-Y SDP with fwts s2idle test 30 times, the system is 
still working.

  [Regression Risk]
  Low. Those patches are all small changes, and most of them are adding IDs, 
should be safe to include them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1819413/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1786139] Re: [GLK/CLX] Enhanced IBRS

[quanxian]

** Changed in: intel
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1786139

Title:
  [GLK/CLX] Enhanced IBRS

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  Description:

  [Impact]

  Future Intel CPU's like Cascade Lake and GLK+ support Enhanced IBRS.
  Enhanced IBRS is a H/W mitigation technique for Spectre V2 bug. So,
  it's important for us to make sure that all the OSV's are using this
  feature.

  The patch that enables kernel support for this feature has been taken
  by Thomas and it's in TIP tree. So, please back port it to all the
  OSV's. Please find the patch here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/pti&id=706d51681d636a0c4a5ef53395ec3b803e45ed4d

  [Test Case]

  For processors that don't support Enhanced IBRS, the test is to ensure
  that /sys/devices/system/cpu/vulnerabilities/spectre_v2 doesn't change
  state after applying the patches. This will typically be the string
  when running on Intel processors that don't support Enhanced IBRS:

    "Mitigation: Full generic retpoline, IBPB, IBRS_FW"

  New Intel processors that do support Enhanced IBRS will display
  "Enhanced IBRS" in place of "Full generic retpoline"

  [Regression Potential]

  Pretty low. The patches are fairly simple and they should only affect
  new processors. The main concern is around the possibility of
  regressing IBRS support on processors that don't support Enhanced IBRS

  Target Kernel:TBD
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1786139/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801014] Re: perf tool needs to support per-die aggregation

[quanxian]

user space perf tools commit ids:
0ccdb8407a4660f6dbc5977bc060917d2c3e7986
acae8b36cded0ee62038dedd0a44d54d5d673a96
b74d8686a18b36adecc710597198d5ef2dd5ef14
db5742b6849ed7f01d764e6755b8ab2b422f29b2
e05a899718f094e2c87d99115c5b1191405a9fd0


** Description changed:

  Description
  Add option "--per-die" to aggregate counts per physical die for CLX-AP and 
CPX.
  For previous platforms, "-per-die" equals to "-per-socket".
  
- Target Kernel:5.3
+ Target package:perf
  Target Release: 19.10

** Package changed: linux (Ubuntu) => perf-tools-unstable (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801014

Title:
  perf tool needs to support per-die aggregation

Status in intel:
  New
Status in perf-tools-unstable package in Ubuntu:
  Incomplete

Bug description:
  Description
  Add option "--per-die" to aggregate counts per physical die for CLX-AP and 
CPX.
  For previous platforms, "-per-die" equals to "-per-socket".

  Target package:perf
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801014/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1825940] Re: [graphics] Enable ICL

[quanxian]

** No longer affects: linux (Ubuntu)

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1825940

Title:
  [graphics] Enable ICL

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  New

Bug description:
  Description:

  ICL graphics is not enabled in 19.04.
  if you want to use 19.04 on ICL platform, you need do like this

  Add kernel option
  i915.alpha_support=1

  Target Release:19.10
  Target Kernel: 5.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1825940/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1771252] Re: [ICL] Enable intel_rapl driver for Icelake

[quanxian]

** No longer affects: linux

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  Desription:
  This feature is intended to track intel_rapl driver enabling for IceLake.
  
  Commit:Powercap/intel_rapl driver enabling for Icelake
  
- Target Release: 19.04
+ Target Release: 19.10
  Target Kernel: 5.1

** Tags removed: intel-kernel-19.04
** Tags added: intel-kernel-19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771252

Title:
  [ICL] Enable intel_rapl driver for Icelake

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  New

Bug description:
  Desription:
  This feature is intended to track intel_rapl driver enabling for IceLake.

  Commit:Powercap/intel_rapl driver enabling for Icelake

  Target Release: 19.10
  Target Kernel: 5.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1771252/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1800999] Re: [ICL] Intel Trace Hub support

[quanxian]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: Fix Committed => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1800999

Title:
  [ICL] Intel Trace Hub support

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  Intel Trace Hub will be used in power on already. We have NPK in both core 
and PCH and that can be routed to give trace data from multiple outputs like 
USB, USB-C and in memory. There might be need to support USB Type-C Debug 
alternate mode.

  Commit ID: 59d08d00d43c

  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1800999/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1800997] Re: [ICL] HS-UART

[quanxian]

** Changed in: intel
   Status: New => Fix Released

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1800997

Title:
  [ICL] HS-UART

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:

  Based on CNL new IDs will be needed.
  CSE DMA access capability to SPI and UART controller.

  Commit Id: a13c93b3a5db

  Target Kernel: 4.19

  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1800997/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801001] Re: [ICL] eMMC support

[quanxian]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: Fix Committed => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801001

Title:
  [ICL] eMMC support

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  ICL meta feature to have all items under this one.

  
  Commit ID: 5637ffadf6719576fcba0e02026f80fd54466265

  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801001/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1821893] Re: [ICL] SD card support

[quanxian]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

** Changed in: intel
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821893

Title:
  [ICL] SD card support

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:

  ICL SD card support feature that is legacy from previous platforms
  most likely validation item only.

  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1821893/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1821885] Re: [ICL] CPUID enable

[quanxian]

** No longer affects: linux

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: Fix Committed => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821885

Title:
  [ICL] CPUID enable

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:

  Enable CPUID of ICL-U/Y/...

  Target Release: 19.04
  Target Kernel: 5.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1821885/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1819413] Re: [ICL] S0ix Enabling

[quanxian]

** No longer affects: linux

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: New => Fix Committed

** Tags removed: intel-kernel-19.04
** Tags added: intel-kernel-19.10

** Description changed:

  Description:
  
  S0ix-states represent the residency in the Intel® SoC idle standby power 
states.
  The S0ix states shut off part of the SoC when they are not in use. The S0ix
  states are triggered when specific conditions within the SoC have been 
achieved,
  for example: certain components are in low power states. The SoC consumes the
  least amount of power in the deepest (for example, S0i3) state.
  
  S0ix is triggered by two paths:
  (1) by system PM, e.g "suspend-to-idle" triggered by pressing the power button
  on Android device or command manually triggered on any Linux based distros;
  
  (2) by runtime PM, i.e no system activities with display off.
  
  S0ix should simply work in theory with trigger path (1) if we have the device
  drivers ready. On GLK, we require the below PCI device drivers with system PM
  support. ACPI device requirements are WIP.
  
-  I2C designware PCI driver 
-  USB XHCI PCI ID 
-  Intel trace Hub[NPK) PCI ID 
-  SPI BXT PCI ID 
-  SCSI UFS BXT PCI host ID 
-  Graphics 
-  Audio 
-  PWM 
-  HSUART 
+  I2C designware PCI driver
+  USB XHCI PCI ID
+  Intel trace Hub[NPK) PCI ID
+  SPI BXT PCI ID
+  SCSI UFS BXT PCI host ID
+  Graphics
+  Audio
+  PWM
+  HSUART
   Security engine
  
  S0ix with trigger path (2) require work as defined below.
   All the above device drivers need to support runtime PM (already defined in 
the same LCK above)
   PCI root port to support runtime PM
  
  Both paths will require intel_idle driver support for S0ix support.
- 
  
  238f9c11351f8af8534ae0318b4d9acc77b09ee8
  
  8aba056a4ea6da18186025a335a96b2f071e69d3
  
  6769fdbe27d782dfee5e459e25b44baacc7c8459
  
  cfb55af9add9c19806300fdb31f4cd25e67c6d1a
  
  4a5861f714293767980e4948c9a7c9e5e09c9b94
  
  2a13096ac7da07a1bfc9d91fc4a982020e7ded2b
  
  cd89e92b7399a69512b8d855a2dd145c47399bf8
  
  d6827015e671cd17871c9b7a0fabe06c044f7470
  
  0e68eeea9894feeba2edf7ec63e4551b87f39621
  
  e50af8332785355de3cb40d9f5e8c45dbfc86f53
  
  Target Kernel: 5.1
- Target Release: 19.04
+ Target Release: 19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1819413

Title:
  [ICL] S0ix Enabling

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  New

Bug description:
  Description:

  S0ix-states represent the residency in the Intel® SoC idle standby power 
states.
  The S0ix states shut off part of the SoC when they are not in use. The S0ix
  states are triggered when specific conditions within the SoC have been 
achieved,
  for example: certain components are in low power states. The SoC consumes the
  least amount of power in the deepest (for example, S0i3) state.

  S0ix is triggered by two paths:
  (1) by system PM, e.g "suspend-to-idle" triggered by pressing the power button
  on Android device or command manually triggered on any Linux based distros;

  (2) by runtime PM, i.e no system activities with display off.

  S0ix should simply work in theory with trigger path (1) if we have the device
  drivers ready. On GLK, we require the below PCI device drivers with system PM
  support. ACPI device requirements are WIP.

   I2C designware PCI driver
   USB XHCI PCI ID
   Intel trace Hub[NPK) PCI ID
   SPI BXT PCI ID
   SCSI UFS BXT PCI host ID
   Graphics
   Audio
   PWM
   HSUART
   Security engine

  S0ix with trigger path (2) require work as defined below.
   All the above device drivers need to support runtime PM (already defined in 
the same LCK above)
   PCI root port to support runtime PM

  Both paths will require intel_idle driver support for S0ix support.

  238f9c11351f8af8534ae0318b4d9acc77b09ee8

  8aba056a4ea6da18186025a335a96b2f071e69d3

  6769fdbe27d782dfee5e459e25b44baacc7c8459

  cfb55af9add9c19806300fdb31f4cd25e67c6d1a

  4a5861f714293767980e4948c9a7c9e5e09c9b94

  2a13096ac7da07a1bfc9d91fc4a982020e7ded2b

  cd89e92b7399a69512b8d855a2dd145c47399bf8

  d6827015e671cd17871c9b7a0fabe06c044f7470

  0e68eeea9894feeba2edf7ec63e4551b87f39621

  e50af8332785355de3cb40d9f5e8c45dbfc86f53

  Target Kernel: 5.1
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1819413/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1819800] Re: ICL-U/Y ISH support

[quanxian]

Add one v4.20-rc1 commit:

71f6fa9 HID: increase maximum global item tag report size to 256

without which it will report errors like

[2.827579] hid (null): invalid report_size 192

** No longer affects: linux

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: Fix Committed => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1819800

Title:
  ICL-U/Y ISH support

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:
  Enable ISH functionality.

  
  Commit IDs:

  9ff3541e3ddf96800ce8fcd225c9e7956da49418

  Target Kernel: 5.0
  Target Release:  19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1819800/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801014] Re: perf tool needs to support per-die aggregation

[quanxian]

** Description changed:

  Description
  Add option "--per-die" to aggregate counts per physical die for CLX-AP and 
CPX.
  For previous platforms, "-per-die" equals to "-per-socket".
  
- Target Release: 19.04
+ Target Release: 19.10

** Tags removed: intel-upkg-19.04
** Tags added: intel-upkg-19.10

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801014

Title:
  perf tool needs to support per-die aggregation

Status in intel:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description
  Add option "--per-die" to aggregate counts per physical die for CLX-AP and 
CPX.
  For previous platforms, "-per-die" equals to "-per-socket".

  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801014/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801221] Re: [Bug]EDAC will not load on systems with greater than 8 sockets

[quanxian]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: Fix Committed => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801221

Title:
  [Bug]EDAC will not load on systems with greater than 8 sockets

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  There is a hard-coded limit of 16 memory controllers. Many of our CPUs have 
two memory controllers per socket, so this means support peaks at 8 sockets.

  There is a temporary Band-Aid patch waiting for next merge window
  (4.20 / 5.0) that just increases this hard limit.
  6b58859419554fb824e09cfdd73151a195473cbc

  Real fix to remove the hard limit will merge into 4.21 (5.1). Probably
  the Band-Aid should be sufficient for backporting to older kernels
  (the real fix will remove from entries from /sys/bus/devices that we
  believe are unused, but kABI sensitive users might not want to take
  that risk).

  Target Kernel:5.0
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801221/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1810876] Re: Add support for Cedar Fork device IDs

[quanxian]

** No longer affects: linux

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

** Changed in: intel
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810876

Title:
  Add support for Cedar Fork device IDs

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:
  Add support for all the relevant Cedar Fork PCH device IDs.

  This task is to identify what new device IDs are required for Cedar Fork, we 
need though to write driver for GPIO.
  SATA, PCIe and USB use class IDs so they should work out of the box so we do 
not need any additional IDs.

  IDs to be added by this JIRA
  Placeholder for Cedar Fork PCH IDs that should be published.

  Device ID intel-next  Kernel Version  Commit  Approved to be published
  SPI-NOR ID: 0x18e0v4.15-rc1   824af37ef2d0
  HS-UART ID: 0x18d8v4.15-rc1   daf3930cf616
  SMBus ID (i2c-801): 0x18dfv4.14-rc4   cb09d943c70d
  SMBus ID (i2c-ismt): 0x18ac   v5.0-rc15cda2d86de3e
  GPIO ACPI ID: INTC3001v4.15-rc1   0f80dbc133e3
  eMMC ID: 0x18db   v4.15-rc1   cdaba732ff2f
  NPK ID: 0x18e1v4.14-rc4   920ce7c33d

  Target Release: 19.04
  Target Kernel: 5.0-rc1

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1810876/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801220] Re: [Bug]unable to handle kernel paging request at 000000006b4fd010

[quanxian]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: Fix Committed => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801220

Title:
  [Bug]unable to handle kernel paging request at 6b4fd010

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  On Multiple Purley (2S/4S) machines, appending "reboot=efi" to the kernel 
boot parameters causes panic during reboot. It happens with upstream kernel as 
well as with RHEL 7.x kernels.

  [ 31.529203] Restarting system.
  [ 31.532261] reboot: machine restart
  [ 31.536474] BUG: unable to handle kernel paging request at 6b4fd010
  [ 31.543458] IP: [] 0xfffeecff9889
  [ 31.548700] PGD 34849063 PUD 3484a063 PMD 0
  [ 31.553038] Oops:  1 SMP
  [ 31.556318] Modules linked in: xfs libcrc32c sd_mod crc_t10dif 
crct10dif_generic crct10dif_pclmul crct10dif_common ahci libahci libata 
dm_mirror dm_region_hash dm_log dm_mod
  [ 31.572112] CPU: 0 PID: 1 Comm: systemd-shutdow Not tainted 
3.10.0-820.el7.x86_64 #1
  [ 31.579832] Hardware name: Intel Corporation PURLEY/PURLEY, BIOS 
SE5C620.86B.01.00.0572.071320170923 07/13/2017
  [ 31.589888] task: 880034a8 ti: 880034a1c000 task.ti: 
880034a1c000
  [ 31.597348] RIP: 0010:[] [] 
0xfffeecff9889
  [ 31.605011] RSP: 0018:880034a1fb30 EFLAGS: 00010006
  [ 31.610311] RAX:  RBX: 880034a1fbf0 RCX: 6b4fd000
  [ 31.617427] RDX:  RSI:  RDI: 880034a1fbd0
  [ 31.624544] RBP: 880034a1fd58 R08: 880034a1fbf0 R09: 880034a1fbd0
  [ 31.631659] R10: fffeecffb1e8 R11: 880034a1fafe R12: 
  [ 31.638774] R13:  R14:  R15: 0002
  [ 31.645889] FS: 7f7c591d5840() GS:88003780() 
knlGS:
  [ 31.653955] CS: 0010 DS:  ES:  CR0: 80050033
  [ 31.673920] DR3:  DR6: fffe0ff0 DR7: 0400
  [ 31.681035] PKRU: 5554
  [ 31.683740] Call Trace:
  [ 31.686187] [] ? kmem_cache_alloc+0x1ba/0x1e0
  [ 31.692183] [] ? acpi_ut_create_generic_state+0x37/0x54
  [ 31.699041] [] ? vsnprintf+0x234/0x6a0
  [ 31.704424] [] ? __const_udelay+0x27/0x30
  [ 31.710070] [] ? serial8250_console_putchar+0x27/0x30
  [ 31.716755] [] ? wait_for_xmitr+0x40/0xa0
  [ 31.722401] [] ? efi_call+0x58/0x90
  [ 31.727527] [] ? up+0x32/0x50
  [ 31.732139] [] virt_efi_reset_system+0x5c/0x110
  [ 31.738301] [] native_machine_emergency_restart+0x182/0x250
  [ 31.745501] [] ? clear_local_APIC+0x12d/0x2a0
  [ 31.751493] [] native_machine_restart+0x37/0x40
  [ 31.757657] [] machine_restart+0xf/0x20
  [ 31.763132] [] kernel_restart+0x45/0x60
  [ 31.768605] [] SYSC_reboot+0x229/0x260
  [ 31.773991] [] ? set_next_entity+0x3c/0xe0
  [ 31.779725] [] ? __switch_to+0x15b/0x590
  [ 31.785283] [] ? __schedule+0x3a4/0x8b0
  [ 31.790756] [] SyS_reboot+0xe/0x10
  [ 31.795798] [] system_call_fastpath+0x16/0x1b
  [ 31.801785] Code: 44 24 40 8b 40 0c b9 04 00 00 00 48 6b c9 00 89 44 0c 20 
48 8b 44 24 40 8b 40 04 25 ff ff 00 00 8b c0 48 6b c0 10 48 8b 4c 24 20 <48> 8b 
44 01 10 48 89 44 24 28 48 8b 44 24 28 48 83 c4 38 c3 cc
  [ 31.822139] RIP [] 0xfffeecff9889
  [ 31.827466] RSP 
  [ 31.830951] CR2: 6b4fd010
  [ 31.834261] --[ end trace 78645683992b62db ]--
  [ 31.868316] Kernel panic - not syncing: Fatal exception
  [ 31.873535] Kernel Offset: disabled
  [ 31.907967] Rebooting in 10 seconds..

  Target Kernel:4.20
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801220/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801219] Re: [SKL]Export XSAVE AVX state in /proc/pid

[quanxian]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  Description
  There is some interest to separate AVX512 using processes from non AVX 
processes to get higher frequency.
  
  A user space tool doing this needs to know whether AVX is used. One way would 
be to export the information from the XSAVE state from the last context switch 
in /proc/pid/*
  Should report if AVX or AVX512 state is non INIT.
  
- Target Kernel: 5.1
- Target Release: 19.04
+ Target Kernel: 5.2
+ Target Release: 19.10

** Tags removed: intel-kernel-19.04
** Tags added: intel-kernel-19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801219

Title:
  [SKL]Export XSAVE AVX state in /proc/pid

Status in intel:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description
  There is some interest to separate AVX512 using processes from non AVX 
processes to get higher frequency.

  A user space tool doing this needs to know whether AVX is used. One way would 
be to export the information from the XSAVE state from the last context switch 
in /proc/pid/*
  Should report if AVX or AVX512 state is non INIT.

  Target Kernel: 5.2
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801219/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1704310] Re: [Bug] Crystal Ridge - null pointer de-reference in device unregister path

[quanxian]

** Package changed: ubuntu => linux (Ubuntu)

** Tags removed: intel-kernel-19.04
** Tags added: intel-kernel-19.10

** Description changed:

  Description:
  
  If I run the following script in a loop, and then ctrl-c it, the kernel
  hits a BUG in the device unregister path.
  
  --[ns-reconf.sh]--
  function pmem_btt_dax_switch() {
  sector_size_list="512 520 528 4096 4104 4160 4224"
  for sector_size in $sector_size_list; do
  ndctl create-namespace -f -e namespace$
  {1}.0 --mode=sector -l $sector_size
  ndctl create-namespace -f -e namespace${1}
  
  .0 --mode=raw
  ndctl create-namespace -f -e namespace$
  {1}
  
  .0 --mode=dax
  done
  }
  for i in 0 1 2 3; do
  pmem_btt_dax_switch $i &
  done
  --[ns-reconf.sh]--
  
  while true; do ./ns-reconfig.sh 0; ./ns-reconfig.sh 1; done
  
  I've tried three times and hit the bug every time, so it seems readily
  reproducible.
  
  Offset 0x20 is the put function pointer in struct klist. This is where
  the null pointer is triggered:
  
  static void klist_put(struct klist_node *n, bool kill)
  {
  struct klist *k = knode_klist;
  void (*put)(struct klist_node *) = k->put; <
  
  This is the tip of Linus' tree, commit be941bf2e6a32.
  
  Any ideas?
  
  -Jeff
  
  [ 117.728323] pmem0s: detected capacity change from 0 to 34093219840
  [ 117.831496] BUG: unable to handle kernel NULL pointer dereference at 
0020
  [ 117.867193] IP: klist_put+0x1b/0x70
  [ 117.884172] PGD 0
  [ 117.884172] P4D 0
  [ 117.894325]
  [ 117.912779] Oops:  1 SMP
  [ 117.926842] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 tun bridge 
stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter 
intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm 
vfat fat irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
aesni_intel crypto_simd nd_pmem iTCO_wdt iTCO_vendor_support glue_helper 
dax_pmem hpilo device_dax lpc_ich hpwdt cryptd nd_btt pcspkr ipmi_si sg ioatdma 
i2c_i801 mfd_core shpchp ipmi_devintf dca wmi ipmi_msghandler nfit 
acpi_power_meter nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables xfs 
sr_mod sd_mod cdrom mgag200 i2c_algo_bit drm_kms_helper syscopyarea
  [ 118.247253] sysfillrect sysimgblt bnx2x fb_sys_fops ahci tg3 mdio ttm 
libahci ptp drm libata i2c_core pps_core hpsa libcrc32c crc32c_intel 
scsi_transport_sas dm_mirror dm_region_hash dm_log dm_mod
  [ 118.326324] CPU: 45 PID: 1060 Comm: kworker/u145:2 Not tainted 4.12.0-rc2+ 
#28
  [ 118.358984] Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS 
P89 10/05/2016
  [ 118.398735] Workqueue: events_unbound async_run_entry_fn
  [ 118.426362] task: 880465ea8000 task.stack: c9000683c000
  [ 118.452949] RIP: 0010:klist_put+0x1b/0x70
  [ 118.470906] RSP: 0018:c9000683fd70 EFLAGS: 00010246
  [ 118.494545] RAX: 880cfdbe8b40 RBX:  RCX: 
00018022001c
  [ 118.526532] RDX: 00018022001d RSI: 0001 RDI: 

  [ 118.558720] RBP: c9000683fd90 R08: 88106463a8e8 R09: 
00018022001c
  [ 118.590772] R10: 6463a701 R11: 88106463a8e8 R12: 
88106935cc00
  [ 118.622923] R13: 880cfdbe8b68 R14: 0001 R15: 
88046f438ce8
  [ 118.655122] FS: () GS:88046fac() 
knlGS:
  [ 118.691517] CS: 0010 DS:  ES:  CR0: 80050033
  [ 118.716914] CR2: 0020 CR3: 01c09000 CR4: 
003406e0
  [ 118.749349] DR0:  DR1:  DR2: 

  [ 118.781627] DR3:  DR6: fffe0ff0 DR7: 
0400
  [ 118.814621] Call Trace:
  [ 118.825740] klist_del+0xe/0x10
  [ 118.839764] device_del+0x11a/0x330
  [ 118.855526] device_unregister+0x1a/0x60
  [ 118.873549] nd_async_device_unregister+0x22/0x30
  [ 118.895091] async_run_entry_fn+0x39/0x170
  [ 118.916718] process_one_work+0x149/0x360
  [ 118.937472] worker_thread+0x4d/0x3c0
  [ 118.953919] kthread+0x109/0x140
  [ 118.968400] ? rescuer_thread+0x380/0x380
  [ 118.986373] ? kthread_park+0x60/0x60
  [ 119.002425] ret_from_fork+0x2c/0x40
  [ 119.018421] Code: e9 1a ff ff ff 90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 
e5 41 56 41 89 f6 41 55 49 89 fd 41 54 53 48 8b 1f 48 83 e3 fe 48 89 df <4c> 8b 
63 20 e8 7c f8 00 00 45 84 f6 75 31 4c 89 ef e8 af fe ff
  [ 119.103298] RIP: klist_put+0x1b/0x70 RSP: c9000683fd70
  [ 119.128194] CR2: 0020
  [ 119.143813] --[ end trace 4fadffd9ed599da8 ]--
  [ 119.169828] Kernel panic - not syncing: Fatal exception
  [ 119.193524] Kernel Offset: disabled
  [ 119.213732] ---[ end Kernel panic - not syncing: Fatal exception
  
  Target Kernel:TBD
- Target Release: 19.04
+ Target Release: 19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is

[Kernel-packages] [Bug 1734081] Re: [Feature] Crystal Ridge: Add a "memory registration with lease" semantic to V4L2

[quanxian]

** Package changed: ubuntu => linux (Ubuntu)

** Tags removed: intel-kernel-19.04
** Tags added: intel-kernel-19.10

** Description changed:

  Description
  
  The Video for Linux v2 API suffers from the same problem as RDMA vs DAX,
  i.e. it wants to established long lived memory registrations. Add a
  semantic that allows the kernel to revoke access to the registration so
  that the elevated page counts are time bounded.
  
- Target Kernel: 4.22
- Target Release: 19.04
+ Target Kernel: 5.2
+ Target Release: 19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1734081

Title:
  [Feature] Crystal Ridge: Add a "memory registration with lease"
  semantic to V4L2

Status in intel:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Description

  The Video for Linux v2 API suffers from the same problem as RDMA vs
  DAX, i.e. it wants to established long lived memory registrations. Add
  a semantic that allows the kernel to revoke access to the registration
  so that the elevated page counts are time bounded.

  Target Kernel: 5.2
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1734081/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1704437] Re: [Bug] Crystal Ridge - libnvdimm: debug create-namespace sysfs collision report from Jeff

[quanxian]

** Package changed: ubuntu => linux (Ubuntu)

** Description changed:

  Description
  
  If you run ndctl create-namespace simultaneously on every cpu on a 72
  cpu system, for exactly the same namespace, things break.  Shocking, I
  know.  I've attached the script and the panic.  Not high priority, I
  don't think.
  
  I tried to attach the shell script, but your email server rejected it.
  So, it's inline below.  Search for thrash-ns.sh.
  
  Cheers,
  Jeff
  
  [   71.912227] ---[ cut here ]---
  [   71.935600] WARNING: CPU: 39 PID: 1039 at fs/sysfs/group.c:237
  sysfs_remove_group+0x8e/0x90
  [   71.978797] sysfs group 'power' not found for kobject 'btt0.1'
  [   72.004940] Modules linked in: xt_CHECKSUM iptable_mangle
  ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat
  nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT
  nf_reject_ipv4 tun bridge stp llc ebtable_filter ebtables
  ip6table_filter ip6_tables iptable_filter intel_rapl sb_edac edac_core
  x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass
  crct10dif_pclmul crc32_pclmul vfat ghash_clmulni_intel fat pcbc
  aesni_intel nd_pmem crypto_simd ipmi_si glue_helper dax_pmem iTCO_wdt
  nd_btt iTCO_vendor_support dax cryptd ipmi_devintf hpwdt lpc_ich hpilo
  pcspkr i2c_i801 ioatdma sg ipmi_msghandler mfd_core wmi shpchp dca nfit
  acpi_power_meter nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables
  xfs sr_mod cdrom sd_mod mgag200 i2c_algo_bit drm_kms_helper syscopyarea
  [   72.326921]  sysfillrect sysimgblt fb_sys_fops ttm bnx2x mdio ahci
  tg3 drm hpsa libahci ptp nvme libata pps_core i2c_core libcrc32c
  crc32c_intel scsi_transport_sas nvme_core dm_mirror dm_region_hash
  dm_log dm_mod
  [   72.411729] CPU: 39 PID: 1039 Comm: kworker/u145:2 Not tainted
  4.11.0-rc1+ #25
  [   72.444221] Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380
  Gen9, BIOS P89 10/05/2016
  [   72.486852] Workqueue: events_unbound async_run_entry_fn
  [   72.512078] Call Trace:
  [   72.523223]  dump_stack+0x63/0x87
  [   72.538230]  __warn+0xd1/0xf0
  [   72.551520]  warn_slowpath_fmt+0x5f/0x80
  [   72.569169]  ? kernfs_find_and_get_ns+0x48/0x60
  [   72.589568]  sysfs_remove_group+0x8e/0x90
  [   72.607495]  dpm_sysfs_remove+0x57/0x60
  [   72.624715]  device_del+0x111/0x350
  [   72.640292]  ? pick_next_task_fair+0x122/0x540
  [   72.660482]  device_unregister+0x1a/0x60
  [   72.678191]  nd_async_device_unregister+0x22/0x30
  [   72.699306]  async_run_entry_fn+0x39/0x170
  [   72.717642]  process_one_work+0x165/0x410
  [   72.735566]  worker_thread+0x137/0x4c0
  [   72.752370]  kthread+0x101/0x140
  [   72.766449]  ? rescuer_thread+0x3b0/0x3b0
  [   72.784357]  ? kthread_park+0x90/0x90
  [   72.800810]  ret_from_fork+0x2c/0x40
  [   72.816960] --[ end trace cb734114d5364186 ]--
  [   72.837661] BUG: unable to handle kernel NULL pointer dereference at
  0020
  [   72.872912] IP: klist_put+0x1b/0x90
  [   72.31] PGD 0
  [   72.31]
  [   72.904390] Oops:  1 SMP
  [   72.918698] Modules linked in: xt_CHECKSUM iptable_mangle
  ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat
  nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT
  nf_reject_ipv4 tun bridge stp llc ebtable_filter ebtables
  ip6table_filter ip6_tables iptable_filter intel_rapl sb_edac edac_core
  x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass
  crct10dif_pclmul crc32_pclmul vfat ghash_clmulni_intel fat pcbc
  aesni_intel nd_pmem crypto_simd ipmi_si glue_helper dax_pmem iTCO_wdt
  nd_btt iTCO_vendor_support dax cryptd ipmi_devintf hpwdt lpc_ich hpilo
  pcspkr i2c_i801 ioatdma sg ipmi_msghandler mfd_core wmi shpchp dca nfit
  acpi_power_meter nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables
  xfs sr_mod cdrom sd_mod mgag200 i2c_algo_bit drm_kms_helper syscopyarea
  [   73.245742]  sysfillrect sysimgblt fb_sys_fops ttm bnx2x mdio ahci
  tg3 drm hpsa libahci ptp nvme libata pps_core i2c_core libcrc32c
  crc32c_intel scsi_transport_sas nvme_core dm_mirror dm_region_hash
  dm_log dm_mod
  [   73.331485] CPU: 39 PID: 1039 Comm: kworker/u145:2 Tainted: G
  W   4.11.0-rc1+ #25
  [   73.370525] Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380
  Gen9, BIOS P89 10/05/2016
  [   73.408108] Workqueue: events_unbound async_run_entry_fn
  [   73.432199] task: 88046523 task.stack: c900061f4000
  [   73.458817] RIP: 0010:klist_put+0x1b/0x90
  [   73.479280] RSP: 0018:c900061f7d68 EFLAGS: 00010246
  [   73.507441] RAX: 88017ccd4b40 RBX:  RCX:
  
  [   73.539498] RDX:  RSI: 0001 RDI:
  
  [   73.571576] RBP: c900061f7d88 R08: fffe R09:
  00047417
  [   73.603526] R10: 0005 R11: 00047416 R12:
  88017ccd4b68
  [   73.635479] R13: 88017d558800 R14: 0001 R15:
  880469cf44b0
  [   73.667484] 

[Kernel-packages] [Bug 1704433] Re: [Feature] Crystal Ridge - Use FS DAX radix tree as a cache to service page faults

[quanxian]

** Package changed: ubuntu => linux (Ubuntu)

** Description changed:

  Description
  
  We already keep the sector in the radix tree as part of the exceptional
  entry. For page faults where we already have an exceptional entry, use
  this information directly from the radix tree instead of calling into
  the filesystem to get a block mapping. This should show a measurable
  performance improvement, which should be reported as motivation for the
  patches.
  
  Target Kernel:TBD
- Target Release: 19.04
+ Target Release: 19.10

** Tags removed: intel-kernel-19.04
** Tags added: intel-kernel-19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1704433

Title:
  [Feature] Crystal Ridge - Use FS DAX radix tree as a cache to service
  page faults

Status in intel:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Description

  We already keep the sector in the radix tree as part of the
  exceptional entry. For page faults where we already have an
  exceptional entry, use this information directly from the radix tree
  instead of calling into the filesystem to get a block mapping. This
  should show a measurable performance improvement, which should be
  reported as motivation for the patches.

  Target Kernel:TBD
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1704433/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1741381] Re: [Feature] Crystal Ridge - dynamic filesystem DAX based on HMAT info

[quanxian]

** Package changed: ubuntu => linux (Ubuntu)

** Tags removed: intel-kernel-19.04
** Tags added: intel-kernel-19.10

** Description changed:

  Description:
  Have the kernel automatically choose whether or not to use filesystem DAX 
based on information in the HMAT. This depends on the outcome of the "mount 
option and inode flag" discussion in the community.
  
- Target Release: 19.04
- Target Kernel:4.20
+ Target Release: 19.10
+ Target Kernel:TBD

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1741381

Title:
  [Feature] Crystal Ridge - dynamic filesystem DAX based on HMAT info

Status in intel:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Description:
  Have the kernel automatically choose whether or not to use filesystem DAX 
based on information in the HMAT. This depends on the outcome of the "mount 
option and inode flag" discussion in the community.

  Target Release: 19.10
  Target Kernel:TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1741381/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1741394] Re: [Feature] Crystal Ridge - get DAX working with XFS realtime devices

[quanxian]

** Package changed: ubuntu => linux (Ubuntu)

** Tags removed: intel-kernel-19.04
** Tags added: intel-kernel-19.10

** Description changed:

  Description
  
  Thus far we haven't had a compelling reason to spend our time making
  sure DAX is working properly with XFS realtime devices, but according to
  some comments on IRC, Darrick Wong is trying it and it isn't working:
  
   now i run into the problem that if the data device doesn't support 
dax then we refuse to enable it on the rt device
   ...also, if the datadev supports it but the rtdev does not, creating 
a dax rt file blow sup
   "pwrite: Operation not supported"
   mmap write just Bus errors
  • djwong discovers __bdev_dax_supported(), wonders why it takes a struct 
super_block * and not a struct block_device *
   i guess the answer is that xfs_fs_fill_super should only disable dax 
if none of the devices support it, and we should only set S_DAX if 
blk_queue_dax(whichever device the file is on)
  
  Fix this and get DAX + realtime devices working.
  
  Target Kernel: TBD
- Target Release: 19.04
+ Target Release: 19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1741394

Title:
  [Feature] Crystal Ridge - get DAX working with XFS realtime devices

Status in intel:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Description

  Thus far we haven't had a compelling reason to spend our time making
  sure DAX is working properly with XFS realtime devices, but according
  to some comments on IRC, Darrick Wong is trying it and it isn't
  working:

   now i run into the problem that if the data device doesn't support 
dax then we refuse to enable it on the rt device
   ...also, if the datadev supports it but the rtdev does not, creating 
a dax rt file blow sup
   "pwrite: Operation not supported"
   mmap write just Bus errors
  • djwong discovers __bdev_dax_supported(), wonders why it takes a struct 
super_block * and not a struct block_device *
   i guess the answer is that xfs_fs_fill_super should only disable dax 
if none of the devices support it, and we should only set S_DAX if 
blk_queue_dax(whichever device the file is on)

  Fix this and get DAX + realtime devices working.

  Target Kernel: TBD
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1741394/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1744634] Re: [Bug]Crystal Ridge - 4.15: fix badblocks routines not merging more than one range at a time

[quanxian]

** Package changed: ubuntu => linux (Ubuntu)

** Description changed:

  Description:
  The badblocks routines we used from md have a bug where if a new range being 
added overlaps with multiple distinct ranges, it only merges with the first one.
  
  Consider the following operations:
  
  badblocks_set(bb, 32, 1);
  badblocks_set(bb, 34, 1);
  badblocks_set(bb, 36, 1);
  
  badblocks_show will now correctly report:
  32 1
  34 1
  36 1
  
  Now if I do:
  badblocks_set(bb, 32, 12);
  
  Ideally, this should collapse all ranges into a single (32, 12).. But
  looks like badblocks_set only merges one set of adjacent mergeable
  ranges, and then returns, resulting in:
  
  32 3
  36 1
  
  Now if I add the same (32, 12) range again, I get:
  
  32 5
  
  as one more set is merged. And finally after adding (32, 12) one final
  time, I get the expected
  
  32 12.
  
  Target Kernel:TBD
- Target Release:19.04
+ Target Release:19.10

** Summary changed:

- [Bug]Crystal Ridge - 4.15: fix badblocks routines not merging more than one 
range at a time
+ [Bug]Crystal Ridge: fix badblocks routines not merging more than one range at 
a time

** Tags removed: intel-kernel-19.04
** Tags added: intel-kernel-19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1744634

Title:
  [Bug]Crystal Ridge: fix badblocks routines not merging more than one
  range at a time

Status in intel:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Description:
  The badblocks routines we used from md have a bug where if a new range being 
added overlaps with multiple distinct ranges, it only merges with the first one.

  Consider the following operations:

  badblocks_set(bb, 32, 1);
  badblocks_set(bb, 34, 1);
  badblocks_set(bb, 36, 1);

  badblocks_show will now correctly report:
  32 1
  34 1
  36 1

  Now if I do:
  badblocks_set(bb, 32, 12);

  Ideally, this should collapse all ranges into a single (32, 12).. But
  looks like badblocks_set only merges one set of adjacent mergeable
  ranges, and then returns, resulting in:

  32 3
  36 1

  Now if I add the same (32, 12) range again, I get:

  32 5

  as one more set is merged. And finally after adding (32, 12) one final
  time, I get the expected

  32 12.

  Target Kernel:TBD
  Target Release:19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1744634/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1774365] Re: ext4: Fix Filesystem-DAX DMA vs Unmap

[quanxian]

** No longer affects: linux

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: New => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1774365

Title:
  ext4: Fix Filesystem-DAX DMA vs Unmap

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:
  Use the new dax_layout_busy_page() and page-idle events to implement block 
unmap versus dma protection in ext4.

  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1774365/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1774385] Re: Add support for Secure Erase, overwrite and enable security

[quanxian]

** Information type changed from Proprietary to Public

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  Description:
  Add support for the new DSMs defined in the DSM spec v1.7.4, including Enable 
NVDIMM Security, Secure Erase NVDIMM, Overwrite NVDIMM and Query Overwrite 
NVDIMM Status.
  
  More info and specs can be found in the CCB:
  
https://vthsd.fm.intel.com/hsd/purley_platform/default.aspx#ccb/default.aspx?ccb_id=136313
  
- Target Kernel: 4.21
+ Target Kernel: 5.0
  
  Target Release: 19.04

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1774385

Title:
  Add support for Secure Erase, overwrite and enable security

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:
  Add support for the new DSMs defined in the DSM spec v1.7.4, including Enable 
NVDIMM Security, Secure Erase NVDIMM, Overwrite NVDIMM and Query Overwrite 
NVDIMM Status.

  More info and specs can be found in the CCB:
  
https://vthsd.fm.intel.com/hsd/purley_platform/default.aspx#ccb/default.aspx?ccb_id=136313

  Target Kernel: 5.0

  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1774385/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1774385] Re: Add support for Secure Erase, overwrite and enable security

[quanxian]

git tag --contains d6548ae4d16d
v5.0
git tag --contains 76ef5e172527
v5.0
git tag --contains 9db67581b91d
v5.0
git tag --contains f2989396553a
v5.0
git tag --contains 37833fb7989a
v5.0
git tag --contains 4c6926a23b76
v5.0
git tag --contains 03b65b22ada8
v5.0
git tag --contains d2a4ac73f56a
v5.0
git tag --contains 64e77c8c047f
v5.0
git tag --contains 7d988097c546
v5.0
git tag --contains 89fa9d8ea7bd
v5.0
git tag --contains 3c13e2ac747a
v5.0
git tag --contains 926f74802cb1
v5.0
git tag --contains ecaa4a97b390
v5.0
git tag --contains 1f4883f300da
v5.0
git tag --contains 37379cfc661e
v5.0


** Changed in: intel
   Status: Triaged => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1774385

Title:
  Add support for Secure Erase, overwrite and enable security

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:
  Add support for the new DSMs defined in the DSM spec v1.7.4, including Enable 
NVDIMM Security, Secure Erase NVDIMM, Overwrite NVDIMM and Query Overwrite 
NVDIMM Status.

  More info and specs can be found in the CCB:
  
https://vthsd.fm.intel.com/hsd/purley_platform/default.aspx#ccb/default.aspx?ccb_id=136313

  Target Kernel: 5.0

  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1774385/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801235] Re: [AEP]2LM performance mitigation: non-self-conflicting numa nodes

[quanxian]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: New => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801235

Title:
  [AEP]2LM performance mitigation: non-self-conflicting numa nodes

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  Extend the numa_emulation driver to allow uniform split of physical numa 
nodes based on a given value.

  3b6c62f363a1 cc9aec03e58f

  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801235/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801245] Re: [AE{]Prevent any ARS attempts when capabilities are clear

[quanxian]

** No longer affects: linux

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: Fix Committed => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801245

Title:
  [AE{]Prevent any ARS attempts when capabilities are clear

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  The v4.17 ARS reworks broke the kernel's honoring of "no ARS capability" 
responses from the BIOS. The kernel unconditionally schedules ARS for all PMEM 
regions. Fix up the implementation to fail all ARS when no capability is 
present.

  Ideally the BIOS would just not publish the DSMs, for ARS, but we
  should handle capabilities being present or not regardless.

  Target Kernel: 4.20
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801245/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801246] Re: [AEP]WARN triggered by the device-dax unit test with 4.19-rc1

[quanxian]

Fix added in 4.19-rc6:

commit 41c9b1be335b5afc3b5fb71c5d16f9d5939cd13f
Author: Dave Jiang 
Date: Mon Sep 10 16:18:29 2018 -0700

device-dax: Add missing address_space_operations

With address_space_operations missing for device dax, namely the
.set_page_dirty, we hit a kernel warning when running destructive
ndctl unit test: make TESTS=device-dax check

WARNING: CPU: 3 PID: 7380 at fs/buffer.c:581 __set_page_dirty+0xb1/0xc0

Setting address_space_operations to noop_set_page_dirty and
noop_invalidatepage for device dax to prevent fallback to
__set_page_dirty_buffers() and block_invalidatepage() respectively.

Fixes: 2232c6382a ("device-dax: Enable page_mapping()")

Acked-by: Jeff Moyer 
Reported-by: Vishal Verma 
Signed-off-by: Dave Jiang 
Signed-off-by: Dan Williams 

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

** Changed in: intel
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801246

Title:
  [AEP]WARN triggered by the device-dax unit test with 4.19-rc1

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  [ +0.003470] WARNING: CPU: 3 PID: 7380 at fs/buffer.c:581 
__set_page_dirty+0xb1/0xc0
  [ +0.001177] Modules linked in: nd_pmem(O) dax_pmem(O) device_dax(O) 
nd_btt(O) nd_e820(O) nfit(O) libnvdimm(O) nfit_test_iomap(O)
  [ 0.001941] CPU: 3 PID: 7380 Comm: lt-device-dax Tainted: G O 4.19.0-rc1 #3
  [ +0.001423] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org 04/01/2014
  [ +0.002023] RIP: 0010:__set_page_dirty+0xb1/0xc0
  [ +0.000789] Code: 80 00 5b 4c 89 e6 48 89 ef 5d 41 5c 41 5d 41 5e e9 a4 ac 
82 00 48 8b 00 f6 c4 02 74 d7 48 89 df e8 54 bb f6 ff 48 89 c6 eb ce <0f> 0b eb 
92 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 41 55
  [ +0.003122] RSP: 0018:c90001bbba38 EFLAGS: 00010046
  [ +0.000911] RAX: 007fff800815 RBX: ea0008108000 RCX: eb851eb851eb851f
  [ +0.001212] RDX:  RSI: 880310c51560 RDI: 0046
  [ +0.001203] RBP: 880310c51548 R08:  R09: 0001
  [ +0.001220] R10: c90001bbb9a8 R11: b200 R12: 0246
  [ +0.001202] R13: 880310c51540 R14: 0001 R15: 88016dd68040
  [ +0.001205] FS: 7f418f6cf780() GS:880311a0() 
knlGS:
  [ +0.001363] CS: 0010 DS:  ES:  CR0: 80050033
  [ +0.000975] CR2: 7f418f6ee000 CR3: 0001a1a36003 CR4: 001606e0
  [ +0.001217] Call Trace:
  [ +0.000435] __set_page_dirty_buffers+0xad/0x100
  [ +0.000791] set_page_dirty_lock+0x41/0x60
  [ +0.000709] dio_bio_complete+0x12c/0x160
  [ +0.000693] ? do_blockdev_direct_IO+0x1c8b/0x2b60
  [ +0.000825] do_blockdev_direct_IO+0x1d29/0x2b60
  [ +0.000827] ? ext4_dio_get_block_unwritten_sync+0x50/0x50
  [ +0.000944] ? ext4_direct_IO+0x15a/0x790
  [ +0.000681] ext4_direct_IO+0x15a/0x790
  [ +0.000672] ? touch_atime+0xc6/0xd0
  [ +0.000621] generic_file_read_iter+0xbb/0xd40
  [ +0.000762] ? up_write+0x1c/0x80
  [ +0.000565] ? ext4_file_write_iter+0x20d/0x400
  [ +0.000789] __vfs_read+0x112/0x190
  [ +0.000619] vfs_read+0x9e/0x150
  [ +0.000418] ksys_pread64+0x74/0x90
  [ +0.000505] do_syscall_64+0x60/0x210
  [ +0.000466] entry_SYSCALL_64_after_hwframe+0x49/0xbe
  [ +0.000618] RIP: 0033:0x7f418e7a1f63
  [ +0.000437] Code: f3 a9 f2 ff e8 4e 5b 02 00 66 2e 0f 1f 84 00 00 00 00 00 
0f 1f 40 00 83 3d e9 d8 2d 00 00 75 13 49 89 ca b8 11 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 34 c3 48 83 ec 08 e8 6b 15 02 00 48 89 04 24
  [ +0.002233] RSP: 002b:7ffc3fb777e8 EFLAGS: 0246 ORIG_RAX: 
0011
  [ +0.000916] RAX: ffda RBX: 7f418f6ea000 RCX: 7f418e7a1f63
  [ +0.000879] RDX: 1000 RSI: 7f418f6ea000 RDI: 0005
  [ +0.000896] RBP:  R08: 001b R09: 
  [ +0.000884] R10:  R11: 0246 R12: 0005
  [ +0.000879] R13:  R14: 0004 R15: 2000
  [ +0.000889] irq event stamp: 136672
  [ +0.000443] hardirqs last enabled at (136671): [] 
_raw_spin_unlock_irqrestore+0x32/0x60
  [ +0.001185] hardirqs last disabled at (136672): [] 
_raw_spin_lock_irqsave+0x22/0x80
  [ +0.001120] softirqs last enabled at (136542): [] 
__do_softirq+0x32e/0x428
  [ +0.001028] softirqs last disabled at (136535): [] 
irq_exit+0xf6/0x100
  [ +0.000995] --[ end trace 2dbcab5579c2e08f ]--

  $ git bisect log 
  git bisect start

  good: [021c91791a5e7e85c567452f1be3e4c2c6cb6063] Linux 4.18-rc3
  git bisect good 021c91791a5e7e85c567452f1be3e4c2c6cb6063
  bad: [c953cc987ab87d180e1d5de2f1c217abe33aac77] libnvdimm, pmem: Restore page 
attributes when clearing errors
  git bisec

[Kernel-packages] [Bug 1801248] Re: [AEP]Add micro-optimizations to dax page pinning

[quanxian]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: Fix Committed => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801248

Title:
  [AEP]Add micro-optimizations to dax page pinning

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  We think we can save a few cpu cycles when pinning user pages mmap'ed from 
dax by avoiding the memtype_lock when looking up the memory type, and cache the 
dev_pagemap structure so we don't need to search the radix tree for it for 
every page.

  Commits:
  df06b37ffe5a442503b7095b77b0a970df515459 
  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801248/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801249] Re: [AEP]softlockup running dax.sh against latest ext4 dev tree

[quanxian]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: New => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801249

Title:
  [AEP]softlockup running dax.sh against latest ext4 dev tree

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  Investigate the lockup report running dax.sh against ext4.

  [ 17.232155] pmem2: detected capacity change from 0 to 134232408064
  [ 238.399253] EXT4-fs (pmem0): DAX enabled. Warning: EXPERIMENTAL, use at 
your own risk
  [ 238.404495] EXT4-fs (pmem0): mounted filesystem with ordered data mode. 
Opts: dax
  [ 238.460013] Injecting memory failure for pfn 0x208900 at process virtual 
address 0x7f38f190
  [ 238.462987] Memory failure: 0x208900: Killing dax-pmd:12226 due to hardware 
memory corruption
  [ 238.465781] Memory failure: 0x208900: recovery action for dax page: 
Recovered
  [ 264.699441] watchdog: BUG: soft lockup - CPU#6 stuck for 22s! 
[dax-pmd:12226]
  [..]
  [ 264.714244] hardirqs last enabled at (106241291): [] 
_raw_spin_unlock_irq+0x29/0x40
  [ 264.717185] hardirqs last disabled at (106241292): [] 
trace_hardirqs_off_thunk+0x1a/0x1c
  [ 264.720163] softirqs last enabled at (106237250): [] 
__do_softirq+0x32e/0x428
  [ 264.722974] softirqs last disabled at (106237243): [] 
irq_exit+0xf6/0x100
  [ 264.725701] CPU: 6 PID: 12226 Comm: dax-pmd Tainted: G OE 4.19.0-rc3+ #2350
  [ 264.728398] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org 04/01/2014
  [ 264.731851] RIP: 0010:lock_is_held_type+0x46/0x60
  [..]
  [ 264.757670] Call Trace:
  [ 264.758745] find_get_entries+0x195/0x3c0
  [ 264.760133] pagevec_lookup_entries+0x1a/0x30
  [ 264.761597] dax_layout_busy_page+0x9c/0x280
  [ 264.763038] ? __lock_acquire+0x12fa/0x1310
  [ 264.764469] ext4_break_layouts+0x48/0x100
  [ 264.765869] ? ext4_punch_hole+0x108/0x5a0
  [ 264.767267] ext4_punch_hole+0x110/0x5a0
  [ 264.768646] ext4_fallocate+0x189/0xa40
  [ 264.76] ? rcu_read_lock_sched_held+0x6b/0x80
  [ 264.771532] ? rcu_sync_lockdep_assert+0x2e/0x60
  [ 264.773040] vfs_fallocate+0x13f/0x270
  [ 264.774373] ksys_fallocate+0x3c/0x70
  [ 264.775694] __x64_sys_fallocate+0x1a/0x20
  [ 264.777094] do_syscall_64+0x60/0x210
  [ 264.778417] entry_SYSCALL_64_after_hwframe+0x49/0xbe

  Commits:
  d7782145e1ad f52afc93cd01

  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801249/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801250] Re: [AEP] mprotect clobbers _PAGE_DEVMAP

[quanxian]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: New => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801250

Title:
  [AEP] mprotect clobbers _PAGE_DEVMAP

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  [PATCH] mm: Preserve _PAGE_DEVMAP across mprotect() calls

  Commits:
  4628a64591e6

  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801250/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801244] Re: [AEP]Need to issue quick ARS if ARS came from ACPI uc error notification and ARS is already running

[quanxian]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: New => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801244

Title:
  [AEP]Need to issue quick ARS if ARS came from ACPI uc error
  notification and ARS is already running

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  If the poison creation path is executed while ARS is running as a background 
task, the call to Start ARS DSM with Flag1=1 will fail with ARS already in 
progress error. Likewise the following Start ARS DSM would also fail. How does 
linux handle this? After ARS background thread has completed, does linux know 
that there could still be unreported errors and re-execute the quick ARS to 
catch any remaining errors?

  Commits:
  cc3d3458d46f

  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801244/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801254] Re: [AEP]EDAC may report the wrong DIMM when patrol scrubber finds an error

[quanxian]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: New => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801254

Title:
  [AEP]EDAC may report the wrong DIMM when patrol scrubber finds an
  error

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  Facebook reported that on Broadwell systems EDAC sometimes reports the wrong 
DIMM for a memory error found by the patrol scrubber.

  The issue is rooted in h/w that only provides a 4KB page aligned
  address for the error in this case. This means that the EDAC driver
  will point at the DIMM matching offset 0x0 in the 4KB page, but
  because of interleaving across channels and ranks the actual DIMM
  involved may be different if the error is on some other cache line
  within the page.

  Fix: We can't actually get EDAC to point to the right DIMM because we
  don't know the offset within the page. But we should fix EDAC to say
  "I don't know" instead of pointing to the wrong DIMM.

  We can check the MCi_MISC register to know whether the address was
  cache-line aligned or page aligned. Bits 5:0 give the least
  significant bit that is valid. So a value of 6 is for cache line
  aligned (8 on Optane DC equipped systems that bundle 4 processor cache
  lines into a single Optane DC cache line). It will be 12 for patrol
  scrubber reported errors.

  Once we know we have a problem we should see how much information we
  can provide just from the "mce" structure passed the the EDAC driver.

  1) We can get the socket from looking at m->extcup (the CMCI from the
  patrol scrubber will have been delivered to a logical CPU on the same
  socket)

  2) The memory controller number. I think the m->bank will tell us this
  Need to check in the EDS for IvyBridge, Haswell and Broadwell.

  3) The channel number. Low bits of MCi_STATUS.MCACOD should provide
  this.

  Facebook said that for many of their systems this should be enough for
  them (as a lot of systems only have one DIMM populated per channel).

  Note that Skylake is allegedly unaffected as the patrol scrubber
  should provide a cacheline aligned address. We should test and confirm

  Commits:
  8489b17ce29d9a35a36c08bbea93cdce4c98a6ad
  Target Kernel: 4.20
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801254/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801256] Re: [AEP]nd_region region12: allocation underrun: 0x0 of 0x1980000000 bytes

[quanxian]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: New => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801256

Title:
  [AEP]nd_region region12: allocation underrun: 0x0 of 0x198000
  bytes

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  This was seen by a customer when trying to create a namespace:

  [1124286.189585] nd_region region12: allocation underrun: 0x0 of 0x198000 
bytes
  [1124286.189604] ---[ cut here ]---
  [1124286.189611] WARNING: CPU: 59 PID: 145367 at 
drivers/nvdimm/namespace_devs.c:913 size_store+0x85e/0x870
  [1124286.189612] Modules linked in: hfsplus hfs isofs binfmt_misc vtsspp(OE) 
sep4_1(OE) sepint4_1(OE) socperf2_0(OE) pax(OE) ip6t_rpfilter ip6t_REJECT 
nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge 
stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 
ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_raw 
iptable_security ebtable_filter ebtables ip6table_filter ip6_tables sunrpc vfat 
fat dax_pmem nd_pmem device_dax nd_btt intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel intel_cstate intel_uncore intel_rapl_perf ipmi_ssif 
iTCO_wdt iTCO_vendor_support ioatdma mei_me joydev i2c_i801 lpc_ich shpchp
  [1124286.189645] mei wmi dca ipmi_msghandler nfit acpi_power_meter acpi_pad 
xfs libcrc32c ast i2c_algo_bit drm_kms_helper ttm crc32c_intel nvme i40e drm 
nvme_core ptp pps_core [last unloaded: vtsspp]
  [1124286.189656] CPU: 59 PID: 145367 Comm: ndctl Tainted: G OE 
4.14.18-300.fc27.x86_64 #1
  [1124286.189657] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS 
SE5C620.86B.01.00.0694.120620170818 12/06/2017
  [1124286.189658] task: 98a64a088000 task.stack: a9840e52
  [1124286.189660] RIP: 0010:size_store+0x85e/0x870
  [1124286.189661] RSP: 0018:a9840e523d38 EFLAGS: 00010282
  [1124286.189662] RAX: 0042 RBX: 9991b119a008 RCX: 

  [1124286.189663] RDX:  RSI: 98a67efd6a38 RDI: 
98a67efd6a38
  [1124286.189663] RBP: 9991b15a3fc0 R08: 0760 R09: 
0004
  [1124286.189664] R10: f171b9971c40 R11: 0001 R12: 

  [1124286.189665] R13: 9991b515f000 R14: 9991b515f3d0 R15: 
a9840e523d9e
  [1124286.189666] FS: 7f402255c780() GS:98a67efc() 
knlGS:
  [1124286.189667] CS: 0010 DS:  ES:  CR0: 80050033
  [1124286.189667] CR2: 563419868608 CR3: 002ef88ac001 CR4: 
007606e0
  [1124286.189668] DR0:  DR1:  DR2: 

  [1124286.189669] DR3:  DR6: fffe0ff0 DR7: 
0400
  [1124286.189669] PKRU: 5554
  [1124286.189670] Call Trace:
  [1124286.189677] ? __kmalloc+0x199/0x210
  [1124286.189680] kernfs_fop_write+0x10b/0x190
  [1124286.189683] __vfs_write+0x36/0x180
  [1124286.189687] ? selinux_file_permission+0x116/0x130
  [1124286.189691] ? security_file_permission+0x3c/0xb0
  [1124286.189692] vfs_write+0xad/0x1a0
  [1124286.189694] SyS_write+0x52/0xc0
  [1124286.189698] do_syscall_64+0x75/0x180
  [1124286.189701] entry_SYSCALL_64_after_hwframe+0x21/0x86
  [1124286.189703] RIP: 0033:0x7f40218517a4
  [1124286.189703] RSP: 002b:7ffcc1c0e948 EFLAGS: 0246 ORIG_RAX: 
0001
  [1124286.189704] RAX: ffda RBX: 000e RCX: 
7f40218517a4
  [1124286.189705] RDX: 000e RSI: 7ffcc1c0e990 RDI: 
0003
  [1124286.189706] RBP: 7ffcc1c0e990 R08: 000a R09: 

  [1124286.189706] R10:  R11: 0246 R12: 
0003
  [1124286.189707] R13:  R14: 7f402255c6b0 R15: 
0002
  [1124286.189708] Code: 48 85 ed 75 04 49 8b 6d 10 4c 89 ef e8 2c a7 fc ff 4c 
8b 44 24 38 4c 89 e1 48 89 ea 48 89 c6 48 c7 c7 a8 7b 0f 95 e8 5d 74 b5 ff <0f> 
ff e9 bb fd ff ff e8 f6 9c af ff 66 0f 1f 44 00 00 0f 1f 44 
  [1124286.189729] --[ end trace 39a78a4960fc8601 ]--

  Commits:
  12e3129e29b4 1e687220ef2d

  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801256/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801668] Re: [AEP] ndctl test failed (21/24) and latest commits needed

[quanxian]

** Changed in: intel
   Status: Fix Committed => Fix Released

** No longer affects: linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801668

Title:
  [AEP] ndctl test failed (21/24) and latest commits needed

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  Description:

  ndctl testing for AEP:

  make --no-print-directory check-TESTS
  FAIL: libndctl
  FAIL: dsm-fail
  PASS: dpa-alloc
  PASS: parent-uuid
  PASS: multi-pmem
  PASS: create.sh
  PASS: clear.sh
  PASS: pmem-errors.sh
  PASS: daxdev-errors.sh
  PASS: multi-dax.sh
  PASS: btt-check.sh
  PASS: label-compat.sh
  PASS: blk-exhaust.sh
  PASS: sector-mode.sh
  PASS: inject-error.sh
  PASS: btt-errors.sh
  PASS: hugetlb
  PASS: btt-pad-compat.sh
  PASS: firmware-update.sh
  PASS: ack-shutdown-count-set
  PASS: rescan-partitions.sh
  FAIL: inject-smart.sh
  PASS: monitor.sh
  PASS: max_available_extent_ns.sh
  make[5]: Nothing to be done for `all'.
  
  Testsuite summary for ndctl 62+
  
  # TOTAL: 24
  # PASS:  21
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  3
  # XPASS: 0
  # ERROR: 0
  
  See test/test-suite.log
  Please report to linux-nvd...@lists.01.org
  
  make[4]: *** [test-suite.log] Error 1
  make[3]: *** [check-TESTS] Error 2
  make[2]: *** [check-am] Error 2
  make[1]: *** [check-recursive] Error 1
  make: *** [check] Error 2

  Reproduce Steps:
  1. Build and install kernel
  when doing ndctl testing, this need kernel ndctl test kernel module support.
  a.Download source kernel
  For exmaple:
  wget https://packages.ubuntu.com/cosmic/linux-source-4.18.0 
  or git clone git://kernel.ubuntu.com/ubuntu/ubuntu-cosmic.git

  b.Configure, build and install kernel
  # yes ''|make oldconfig
  # Ubuntu set CONFIG_LIBNVDIMM to ‘M’
  make menuconfig -> Processor type and features -> Support non-standard 
NVDIMMs and ADR protected memory  set to 'm' (Turn down two pages)

  # make –j`nproc`
  # make M=tools/testing/nvdimm
  # make M=tools/testing/nvdimm modules_install
  # make modules_install
  # make install

  2. download ndctl source package
  download from github
  https://github.com/pmem/ndctl

  3) Build ndctl test package
  # apt install –y autogen autoconf libopenr2-bin automake ranlib nvptx-tools 
libtool asciidoctor libkmod-dev libkmod2 libudev-dev uuid-dev libcjson-dev 
libjson-c-dev
  # rpmbuild –bp ndctl.spec
  # cd ./BUILD/ndctl-62
  # export LC_ALL=C (for Ubuntu)
  # ./autogen.sh
  # ./ configure CFLAGS='-g -O2' --prefix=/usr --sysconfdir=/etc 
--libdir=/usr/lib64 --with-systemd-unit-dir  --enable-test
  # export KVER=4.20.0
  # yum install jq
  # make check

  Commits related with failed test case:

  b4d4702f30e0 tools/testing/nvdimm: improve emulation of smart injection
  39611e83a28c tools/testing/nvdimm: Make DSM failure code injection an override
  099b07a25fff acpi, nfit: Prefer _DSM over _LSR for namespace label reads
  08e6b3c6e3a0 libnvdimm: Introduce locked DIMM capacity support
  41cd8b70c37a libnvdimm, btt: add support for blk integrity
  5e096ef3b29e6113a7aa6a7dc4871987efa99bcb nfit_test: when clearing poison, 
also remove badrange entries
  89360b87c3efa5d265a3b43dd8fc245c8f4356e3 libnvdimm, badrange: remove a WARN 
for list_empty
  9fb1a1903345fea598f48277576a3589a972b72e nfit_test: add error injection DSMs
  aa9ad44a42b4cf4387f8ecddaf8e51707fdcda5a libnvdimm: move poison list 
functions to a new 'badrange' file

  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801668/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801251] Re: [AEP]Fix badblocks population for 'raw' namespaces

[quanxian]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: Fix Committed => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801251

Title:
  [AEP]Fix badblocks population for 'raw' namespaces

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  The driver is only initializing bb_res in the devm_memremap_pages()
  paths, but the raw namespace case is passing an uninitialized bb_res to
  nvdimm_badblocks_populate().

  Fixes: e8d513483300 ("memremap: change devm_memremap_pages interface...")
  Cc: 
  Cc: Christoph Hellwig 
  Reported-by: Jacek Zloch 
  Reported-by: Krzysztof Rusocki 
  Reviewed-by: Vishal Verma 
  Signed-off-by: Dan Williams 

  Target Release: 19.04
  Target Kernel: 4.20

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801251/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801253] Re: [AEP]copy_to_iter_mcsafe() send incorrect param to check_copy_size()

[quanxian]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: New => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801253

Title:
  [AEP]copy_to_iter_mcsafe() send incorrect param to check_copy_size()

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  copy_to_iter_mcsafe() is passing in the is_source parameter as "false" to 
check_copy_size(). This is different than what copy_to_iter() does. Also, the 
addr parameter passed to check_copy_size() is the source so therefore we should 
be passing in "true" instead.

  Commits:
  dfb06cba8c73

  Target Kernel: 4.19
  Target Release:  19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801253/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1823588] Re: [bug]kernel_physical_mapping_init regression in v4.20-rc1

[quanxian]

git tag --contains  ba6f508d0ec4
v5.0
v5.0-rc1
v5.0-rc2
...

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823588

Title:
  [bug]kernel_physical_mapping_init regression in v4.20-rc1

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:
  A new warning introduced in v4.20-rc1 is triggered by the pmem use case for 
memory hotplug:

  WARNING: CPU: 3 PID: 998 at arch/x86/include/asm/tlbflush.h:460
  __flush_tlb_all+0x1b/0x3a

  The fix is to drop those __flush_tlb_all calls, but requests to
  strengthen the safety of kernel_physical_mapping_init to give
  confidence that it is safe to remove those calls is thus far leading
  to boot hangs.

  Commits in next:(should be in 5.1, after merged, commit id will be changed)
  ba6f508d0ec4 x86/mm: Drop usage of __flush_tlb_all() in 
kernel_physical_mapping_init()
  0a9fe8ca844d x86/mm: Validate kernel_physical_mapping_init() PTE population
  4369deaa2f02 generic/pgtable: Introduce set_pte_safe()
  0cebbb60f759 generic/pgtable: Introduce {p4d,pgd} _same()
  c683c37cd132 generic/pgtable: Make {pmd, pud} _same() unconditionally 
available
  ba6f508d0ec4 x86/mm: Drop usage of __flush_tlb_all() in 
kernel_physical_mapping_init()

  Targeted Release: 19.04
  Targeted Kernel: 5.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1823588/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1823588] Re: [bug]kernel_physical_mapping_init regression in v4.20-rc1

[quanxian]

ba6f508d0ec4 x86/mm: Drop usage of __flush_tlb_all() in
kernel_physical_mapping_init()

** No longer affects: linux

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: New => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

** Description changed:

  Description:
  A new warning introduced in v4.20-rc1 is triggered by the pmem use case for 
memory hotplug:
  
  WARNING: CPU: 3 PID: 998 at arch/x86/include/asm/tlbflush.h:460
  __flush_tlb_all+0x1b/0x3a
  
  The fix is to drop those __flush_tlb_all calls, but requests to
  strengthen the safety of kernel_physical_mapping_init to give confidence
  that it is safe to remove those calls is thus far leading to boot hangs.
  
  Commits in next:(should be in 5.1, after merged, commit id will be changed)
  ba6f508d0ec4 x86/mm: Drop usage of __flush_tlb_all() in 
kernel_physical_mapping_init()
  0a9fe8ca844d x86/mm: Validate kernel_physical_mapping_init() PTE population
  4369deaa2f02 generic/pgtable: Introduce set_pte_safe()
  0cebbb60f759 generic/pgtable: Introduce {p4d,pgd} _same()
  c683c37cd132 generic/pgtable: Make {pmd, pud} _same() unconditionally 
available
  ba6f508d0ec4 x86/mm: Drop usage of __flush_tlb_all() in 
kernel_physical_mapping_init()
  
- Targeted Release: 19.10
- Targeted Kernel: 5.1
+ Targeted Release: 19.04
+ Targeted Kernel: 5.0

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823588

Title:
  [bug]kernel_physical_mapping_init regression in v4.20-rc1

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:
  A new warning introduced in v4.20-rc1 is triggered by the pmem use case for 
memory hotplug:

  WARNING: CPU: 3 PID: 998 at arch/x86/include/asm/tlbflush.h:460
  __flush_tlb_all+0x1b/0x3a

  The fix is to drop those __flush_tlb_all calls, but requests to
  strengthen the safety of kernel_physical_mapping_init to give
  confidence that it is safe to remove those calls is thus far leading
  to boot hangs.

  Commits in next:(should be in 5.1, after merged, commit id will be changed)
  ba6f508d0ec4 x86/mm: Drop usage of __flush_tlb_all() in 
kernel_physical_mapping_init()
  0a9fe8ca844d x86/mm: Validate kernel_physical_mapping_init() PTE population
  4369deaa2f02 generic/pgtable: Introduce set_pte_safe()
  0cebbb60f759 generic/pgtable: Introduce {p4d,pgd} _same()
  c683c37cd132 generic/pgtable: Make {pmd, pud} _same() unconditionally 
available
  ba6f508d0ec4 x86/mm: Drop usage of __flush_tlb_all() in 
kernel_physical_mapping_init()

  Targeted Release: 19.04
  Targeted Kernel: 5.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1823588/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1782206] Re: KVM enable SnowRidge Accelerator Interfacing Architecture (AIA)

[quanxian]

** Description changed:

  CPU core (Tremont) includes Accelerator Interfacing Architecture (AIA) 
features including:
  - UMONITOR/UMWAIT: Ring-3 MONITOR/MWAIT with timeout. For memory-based synch 
with accelerators
  - TPAUSE: Monitor-less wait (with timeout). For wait-on-multiple or 
wait-for-interrupt usages
  - MOVDIRI: 8B streaming doorbell write capability. For streaming accelerator 
usages.
  - MOVDIR64B: Non-temporal write with 64B guaranteed write-atomicity. For 
latency critical accelerator usages
  
  Upstream target linux 5.1/Qemu-3.10
  
- Target Release: 19.04
+ Target Release: 19.10

** Tags removed: intel-virt-19.04
** Tags added: intel-virt-19.10

** Description changed:

  CPU core (Tremont) includes Accelerator Interfacing Architecture (AIA) 
features including:
  - UMONITOR/UMWAIT: Ring-3 MONITOR/MWAIT with timeout. For memory-based synch 
with accelerators
  - TPAUSE: Monitor-less wait (with timeout). For wait-on-multiple or 
wait-for-interrupt usages
  - MOVDIRI: 8B streaming doorbell write capability. For streaming accelerator 
usages.
  - MOVDIR64B: Non-temporal write with 64B guaranteed write-atomicity. For 
latency critical accelerator usages
  
- Upstream target linux 5.1/Qemu-3.10
+ Upstream target linux 5.3/Qemu-3.10
  
  Target Release: 19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1782206

Title:
  KVM enable SnowRidge Accelerator Interfacing Architecture (AIA)

Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Triaged
Status in xen package in Ubuntu:
  Incomplete

Bug description:
  CPU core (Tremont) includes Accelerator Interfacing Architecture (AIA) 
features including:
  - UMONITOR/UMWAIT: Ring-3 MONITOR/MWAIT with timeout. For memory-based synch 
with accelerators
  - TPAUSE: Monitor-less wait (with timeout). For wait-on-multiple or 
wait-for-interrupt usages
  - MOVDIRI: 8B streaming doorbell write capability. For streaming accelerator 
usages.
  - MOVDIR64B: Non-temporal write with 64B guaranteed write-atomicity. For 
latency critical accelerator usages

  Upstream target linux 5.3/Qemu-3.10

  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782206/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1782205] Re: KVM SnowRidge enable new ISAs

[quanxian]

** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1782205

Title:
  KVM SnowRidge enable new ISAs

Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in xen package in Ubuntu:
  Invalid

Bug description:
  Add KVM support for SnowRidge New Instructions: GFNI and CLDEMOT

  GFNI: New instruction to compute an affine transformation in the Galois Field.
   The instruction is described here:
  
https://software.intel.com/sites/default/files/managed/c5/15/architecture-instruction-set-extensions-programming-reference.pdf

  CLDEMOT: New instruction to hint to hardware that a cache line is
  likely to be shared. This is used to improve core-to-core
  communication.

  Upstream Target is Linux 4.20
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782205/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1782209] Re: KVM SnowRidge Split-lock disable

[quanxian]

** Description changed:

  When bit 29 is set in Test Control MSR register 0x33, a #AC execption
   is generated for split locked accesses at all CPL irrespective of
   CR0.AM or EFLAGS.AC.
  
  This feature can help developers to capture memory accesses that across
  cachelines with #LOCK assertion. Then developers can reconstruct their
  program accordingly
  
  Upstream target linux 5.2
- Target Release: 19.04
+ Target Release: 19.10

** Tags removed: intel-virt-19.04
** Tags added: intel-virt-19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1782209

Title:
  KVM SnowRidge Split-lock disable

Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  New

Bug description:
  When bit 29 is set in Test Control MSR register 0x33, a #AC execption
   is generated for split locked accesses at all CPL irrespective of
   CR0.AM or EFLAGS.AC.

  This feature can help developers to capture memory accesses that
  across cachelines with #LOCK assertion. Then developers can
  reconstruct their program accordingly

  Upstream target linux 5.2
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782209/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801287] Re: [VROC] Update MD RAID drivers to the latest upstream version

[quanxian]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: Fix Committed => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801287

Title:
  [VROC] Update MD RAID drivers to the latest upstream version

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:

  Update MD RAID drivers to the latest upstream version
  Include md/bitmap, raid0, raid1, raid10 and raid456.

  This capability takes advantage of MD's long history and extends it to 
support the Intel Matrix metadata format (IMSM).
  MD provides a path to full Intel Matrix feature compatibility with minimal 
kernel changes.

  MD driver extensions are in active development. Final version will be 
included in Shaohua Li's GIT repository:
  https://git.kernel.org/cgit/linux/kernel/git/shli/md.git/

  Target Release: 19.04
  Target Kernel: 5.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801287/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1685997] Re: [Feature] TPM: TPM 2.0 MEI Driver Update

[quanxian]

** Information type changed from Proprietary to Public

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: Incomplete => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1685997

Title:
  [Feature] TPM: TPM 2.0 MEI Driver Update

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:
  Intel® QAT uses MEI to talk to intel® PTT (Platform Trust Technology – 
firmware TPM.

  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1685997/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1760755] Re: Intel FPGA Phase 1 driver upstream

[quanxian]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  Description:
  The FPGA upstream driver Phase 1 includes the FPGA driver framework and 
minimum function support with basic function can work, end users can write 
apps, image can be flushed and programed. The driver includes below modules:
  
  PCIe driver core
  FME driver core with PR support
  AFU driver core with DMA + region mmap support
  
- Target Release: 18.10
- Target Kernel: 4.17
+ Target Release: 19.10
+ Target Kernel: TBD

** Tags removed: intel-kernel-18.10
** Tags added: intel-kernel-19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1760755

Title:
  Intel FPGA Phase 1 driver upstream

Status in intel:
  Triaged
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:
  The FPGA upstream driver Phase 1 includes the FPGA driver framework and 
minimum function support with basic function can work, end users can write 
apps, image can be flushed and programed. The driver includes below modules:

  PCIe driver core
  FME driver core with PR support
  AFU driver core with DMA + region mmap support

  Target Release: 19.10
  Target Kernel: TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1760755/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1827978] [NEW] [SGX]Flexible Launch Control

[quanxian]

Public bug reported:

Implement open source launch enclave and bundle it with the Linux kernel
so that the kernel can generate launch tokens for enclaves that the user
requests to run.

Flexible Launch Control consists of:

Enclave singing tool for kbuild (DONE)
Launch Enclave and its user space (DONE)
Host program for the LE that reads SIGSTRUCT instances from stdin and outputs 
them to stdout (DONE)
Kbuild changes to generate LE signing key (IN PROGRESS)
Driver changes to launch lehost using user space helper framework (IN PROGRESS)
Kernel changes to link lehost to vmlinux (IN PROGRESS)
Relevant URLs:

Launch enclave and host program: https://github.com/jsakkine-intel/sgx-le
Kernel tree: https://github.com/jsakkine-intel/linux-sgx

Target Kernel: 5.2
Target Release: 19.10

** Affects: intel
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: intel-kernel-19.10

** Description changed:

  Implement open source launch enclave and bundle it with the Linux kernel
  so that the kernel can generate launch tokens for enclaves that the user
  requests to run.
  
  Flexible Launch Control consists of:
  
  Enclave singing tool for kbuild (DONE)
  Launch Enclave and its user space (DONE)
  Host program for the LE that reads SIGSTRUCT instances from stdin and outputs 
them to stdout (DONE)
  Kbuild changes to generate LE signing key (IN PROGRESS)
  Driver changes to launch lehost using user space helper framework (IN 
PROGRESS)
  Kernel changes to link lehost to vmlinux (IN PROGRESS)
  Relevant URLs:
  
  Launch enclave and host program: https://github.com/jsakkine-intel/sgx-le
  Kernel tree: https://github.com/jsakkine-intel/linux-sgx
+ 
+ Target Kernel: 5.2
+ Target Release: 19.10

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1827978

Title:
  [SGX]Flexible Launch Control

Status in intel:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Implement open source launch enclave and bundle it with the Linux
  kernel so that the kernel can generate launch tokens for enclaves that
  the user requests to run.

  Flexible Launch Control consists of:

  Enclave singing tool for kbuild (DONE)
  Launch Enclave and its user space (DONE)
  Host program for the LE that reads SIGSTRUCT instances from stdin and outputs 
them to stdout (DONE)
  Kbuild changes to generate LE signing key (IN PROGRESS)
  Driver changes to launch lehost using user space helper framework (IN 
PROGRESS)
  Kernel changes to link lehost to vmlinux (IN PROGRESS)
  Relevant URLs:

  Launch enclave and host program: https://github.com/jsakkine-intel/sgx-le
  Kernel tree: https://github.com/jsakkine-intel/linux-sgx

  Target Kernel: 5.2
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1827978/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1730885] Re: [Feature] SGX mainline enabling

[quanxian]

** Also affects: ubuntu
   Importance: Undecided
   Status: New

** Package changed: ubuntu => linux (Ubuntu)

** Description changed:

  Description
  
  Umbrella task for SGX mainline kernel features.
  
  Target Kernel: 5.4
- Target Release: 19.04
+ Target Release: 19.10

** Tags removed: intel-kernel-19.04
** Tags added: intel-kernel-19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730885

Title:
  [Feature] SGX mainline enabling

Status in intel:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Description

  Umbrella task for SGX mainline kernel features.

  Target Kernel: 5.4
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730885/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801263] Re: Update to the latest QAT driver

[quanxian]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: New => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801263

Title:
  Update to the latest QAT driver

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:
  Update to the latest QAT driver

  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801263/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1801260] Re: USB Type-C Alternate Mode support

[quanxian]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: New => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801260

Title:
  USB Type-C Alternate Mode support

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  Let's track here the progress for generic alternate mode support. The 
discovery and entering/exiting the modes is common for all alternate modes, and 
the USB PD code will handle that. The tasks currently related to this task are:

  1) The alternate modes will need custom control that we don't want to
  mix into the generic USB PD code. For example the DP altmode defines
  custom VDM (Vendor Defined Message) for "configure" and "status"
  commands. So we will need to create somekind of API for Alternate Mode
  "drivers".

  2) The Alternate Modes need to keep the underlying components and
  drivers informed about their status, possibly even allow some control.
  For example, with DP altmode the graphics side will need to know the
  cable orientation and the number of lanes (the modes define the pin
  configuration in DP altmode, so the numer of available lanes as well
  AFAIK). So we need API for this.

  *) UCSI may need some special attention, as with UCSI we don't handle
  the USB PD communication. We just get the status of the port. But we
  will know which alternate mode has been enterred, and we can actually
  request enter/exit a mode even with UCSI. But we don't know for
  example the cable orientation.

  Commits:
  0e3bb7d6894d9b6e67d6382bb03a46a1dc989588 
49cbb33dfdeb7651b91c2316a61b644d8e6cfe22 
4ab8c18d4d67321cc7b660559de17511d4fc0237 
8a37d87d72f0c69f837229c04d2fcd7117ea57e7 
93dd2112c7b2fa5512cc4aff2c449420487fcb68 
e9576fe8e605c4413beb91b290b8a473985710de 

  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801260/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1730883] Re: [HMEM] Allow persistent memory to be used like normal RAM

[quanxian]

** No longer affects: linux

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730883

Title:
  [HMEM] Allow persistent memory to be used like normal RAM

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  New

Bug description:
  Description

  Persistent memory is cool. But, currently, you have to rewrite
  your applications to use it. Wouldn't it be cool if you could
  just have it show up in your system like normal RAM and get to
  it like a slow blob of memory? Well... have I got the patch
  series for you!

  This series adds a new "driver" to which pmem devices can be
  attached. Once attached, the memory "owned" by the device is
  hot-added to the kernel and managed like any other memory. On
  systems with an HMAT (a new ACPI table), each socket (roughly)
  will have a separate NUMA node for its persistent memory so
  this newly-added memory can be selected by its unique NUMA
  node.

  Target Kernel: 5.1
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730883/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1731408] Re: [Feature] [HMEM] Move device-dax resource reservation to be per-instance

[quanxian]

** No longer affects: linux

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Tags removed: intel-kernel-19.04
** Tags added: intel-kernel-19.10

** Description changed:

  Description
  
  Stop reserving an entire dax-region and let individual instances hold
  the reservation for their range.
  
  Target Kernel: 5.1
- Target Release: 19.04
+ Target Release: 19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1731408

Title:
  [Feature] [HMEM] Move device-dax resource reservation to be per-
  instance

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  New

Bug description:
  Description

  Stop reserving an entire dax-region and let individual instances hold
  the reservation for their range.

  Target Kernel: 5.1
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1731408/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1730872] Re: [Feature][HMEM] hot plug device DAX back into the kernel

[quanxian]

** No longer affects: linux

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Tags removed: intel-kernel-19.04
** Tags added: intel-kernel-19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730872

Title:
  [Feature][HMEM] hot plug device DAX back into the kernel

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:
  Hot plug device DAX back into the kernel.

  Target Kernel: 5.1
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730872/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1730872] Re: [Feature][HMEM] hot plug device DAX back into the kernel

[quanxian]

** Description changed:

  Description:
  Hot plug device DAX back into the kernel.
  
  Target Kernel: 5.1
- Target Release: 19.04
+ Target Release: 19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730872

Title:
  [Feature][HMEM] hot plug device DAX back into the kernel

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:
  Hot plug device DAX back into the kernel.

  Target Kernel: 5.1
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730872/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1730867] Re: [Feature][HMEM] Consume HMAT tables in Linux guest, create sysfs representation

[quanxian]

** Description changed:

  Description:
  
  This is dependent upon these two other Jira features:
  [HMEM] Specify initial sysfs representation for heterogeneous memory
  [HMEM] Update QEMU prototype to the latest HMAT spec, R053
  This task is to consume the newly updated HMAT talbles and create the sysfs 
representation.
  
  Target Kernel: TBD
- Target Release: 19.04
+ Target Release: 19.10

** Tags removed: intel-kernel-19.04
** Tags added: intel-kernel-19.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730867

Title:
  [Feature][HMEM] Consume HMAT tables in Linux guest, create sysfs
  representation

Status in intel:
  New
Status in linux package in Ubuntu:
  Expired
Status in linux source package in Bionic:
  Expired

Bug description:
  Description:

  This is dependent upon these two other Jira features:
  [HMEM] Specify initial sysfs representation for heterogeneous memory
  [HMEM] Update QEMU prototype to the latest HMAT spec, R053
  This task is to consume the newly updated HMAT talbles and create the sysfs 
representation.

  Target Kernel: TBD
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730867/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1730884] Re: [Feature] support 6/8 cbos in uncore driver on CFL

[quanxian]

** No longer affects: linux

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: Fix Committed => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

** Tags removed: intel-kernel-18.10
** Tags added: intel-kernel-19.04

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730884

Title:
  [Feature] support 6/8 cbos in uncore driver on CFL

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description

  CFL has the same model number as KBL, but will have 6 and later 8 cores.
  We need to support the extra CBOs in the client uncore driver.

  There is an enumeration MSR that describes how many CBOs there (but I
  don't know the exact name, need to figure that out). This will handle
  upto 6 cores.

  For 8 cores they ran out of MSR space. The plan currently is to
  enumerate 7 CBOs, and then require the software to check the stepping
  number and enable the 8th CBO. I'll update this feature when the exact
  information on this becomes available.

  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730884/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1820147] Re: Memory bandwidth allocation software controller fixes

[quanxian]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: New => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1820147

Title:
  Memory bandwidth allocation software controller fixes

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:

  This is a bug fix for LP#1774090.

  2cc81c6992248ea37d0241bc325977bab310bc3b x86/intel_rdt: Show missing
  resctrl mount options

  git tag --contains 2cc81c6992248ea37d0241bc325977bab310bc3b
  v4.20

  This should been in 19.04. If 18.10/18.04 need that, you can do a
  backporing.

  Target Kernel: 5.0

  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1820147/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1730872] Re: [Feature][HMEM] hot plug device DAX back into the kernel

[quanxian]

** Tags removed: disco

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730872

Title:
  [Feature][HMEM] hot plug device DAX back into the kernel

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:
  Hot plug device DAX back into the kernel.

  Target Kernel: 5.1
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730872/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1774114] Re: Runtime PM for Thunderbolt host controller (Titan Ridge)

[quanxian]

** No longer affects: linux

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

** Changed in: intel
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1774114

Title:
  Runtime PM for Thunderbolt host controller (Titan Ridge)

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:

  When in RTD3 mode the host controller is present always. In order to
  save power we need to move it to D3 when it is idle.

  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1774114/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1741383] Re: [Feature] Runtime PM for native PCIe hotplug ports

[quanxian]

** Changed in: intel
   Status: Fix Committed => Fix Released

** Changed in: ubuntu
   Status: New => Fix Released

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1741383

Title:
  [Feature] Runtime PM for native PCIe hotplug ports

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:
  Currently we already support runtime PM for PCIe ports but it is explicitly 
disabled for hotplug capable ports. There are many reasons for this:

  1. It will not work well when ACPI based hotplug is used as the SMI handler 
will get confused if the port is powered down.
  2. For native PCIe hotplug there are problems when the slot is enabled 
through sysfs like the one here: 
https://bugzilla.kernel.org/show_bug.cgi?id=193951

  Since we are moving from ACPI based hotplug to native PCIe hotplug in
  case of Thunderbolt, it is essential to get the runtime PM for such
  ports working properly. We should be able to relax the limitation a
  bit and allow runtime PM for native PCIe hotplug ports once 2. above
  has been resolved first.

  Target Release: 19.04

  Target Kernel: 4.19

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1741383/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1792536] Re: [DNV][KBL-NUC]Watchdog can not reboot system

[quanxian]

KBL will use another bug.

** Changed in: intel
   Status: Triaged => Fix Released

** Changed in: linux (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: linux (Ubuntu Cosmic)
   Status: Triaged => Fix Released

** Summary changed:

- [DNV][KBL-NUC]Watchdog can not reboot system
+ [DNV]Watchdog can not reboot system

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1792536

Title:
  [DNV]Watchdog can not reboot system

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Description:
  Watchdog not work on Denverton and KBL-NUC platform.

  Commit IDs:851a15114895c5bce163a6f2d57e0aa4658a1be4
  Target Kernel: 4.19

  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1792536/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1792536] Re: [DNV]Watchdog can not reboot system

[quanxian]

for KBL, it will old watchdog driver. Not a kernel issue.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1792536

Title:
  [DNV]Watchdog can not reboot system

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Description:
  Watchdog not work on Denverton and KBL-NUC platform.

  Commit IDs:851a15114895c5bce163a6f2d57e0aa4658a1be4
  Target Kernel: 4.19

  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1792536/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1823595] Re: [bug]Fix namespace section padding relative to other regions

[quanxian]

ae86cbfef381 e3f5df762d4a

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel
   Status: Fix Committed => Fix Released

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823595

Title:
  [bug]Fix namespace section padding relative to other regions

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:

  Commit cfe30b872058 "libnvdimm, pmem: adjust for section collisions with
  'System RAM'" enabled the libnvdimm core to workaround occasions where
  platform firmware arranges for "System RAM" and "Persistent Memory" to
  collide within a single section boundary. Unfortunately, as reported in
  this issue [1], platform firmware can inflict the same collision between
  persistent memory regions.

  The approach of interrogating iomem_resource does not work in this
  case because platform firmware may merge multiple regions into a single
  iomem_resource range. Instead provide a method to interrogate regions
  that share the same parent bus.

  This is a stop-gap until the core-MM can grow support for hotplug on
  sub-section boundaries.

  [1]: https://github.com/pmem/ndctl/issues/76

  Commits:
  ae86cbfef381 libnvdimm, pfn: Pad pfn namespaces relative to other regions
  e3f5df762d4a tools/testing/nvdimm: Align test resources to 128M

  Target Release: 19.04
  Target Kernel: 5.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1823595/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1835349] Re: Fix devm_memremap_pages shutdown handling

[quanxian]

1570175abd16 2374b6822551 2e3f139e8ece 50f44ee7248a 795ee30648c7
e615a191216e

v5.2

** Description changed:

  Description:
  
  > 1) Some p2pdma user calls pci_alloc_p2pmem() to get some memory to DMA
  > to taking a reference to the pgmap.
  > 2) Another process unbinds the underlying p2pdma driver and the devm
  > chain starts to unwind.
  > 3) devm_memremap_pages_release() is called and it kills the reference
  > and drop's it's last reference.
  
  Oh! Yes, nice find. We need to wait for the percpu-ref to be dead and
  all outstanding references dropped before we can proceed to
  arch_remove_memory(), and I think this problem has been there since
  day one because the final exit was always after devm_memremap_pages()
  release which means arch_remove_memory() was always racing any final
  put_page(). I'll take a look, it seems the arch_remove_pages() call
  needs to be moved out-of-line to its own context and wait for the
  final exit of the percpu-ref.
  
  Target Release: 19.10
- Target Kernel: 5.3
+ Target Kernel: 5.2

** Changed in: intel
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1835349

Title:
  Fix devm_memremap_pages shutdown handling

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:

  > 1) Some p2pdma user calls pci_alloc_p2pmem() to get some memory to DMA
  > to taking a reference to the pgmap.
  > 2) Another process unbinds the underlying p2pdma driver and the devm
  > chain starts to unwind.
  > 3) devm_memremap_pages_release() is called and it kills the reference
  > and drop's it's last reference.

  Oh! Yes, nice find. We need to wait for the percpu-ref to be dead and
  all outstanding references dropped before we can proceed to
  arch_remove_memory(), and I think this problem has been there since
  day one because the final exit was always after devm_memremap_pages()
  release which means arch_remove_memory() was always racing any final
  put_page(). I'll take a look, it seems the arch_remove_pages() call
  needs to be moved out-of-line to its own context and wait for the
  final exit of the percpu-ref.

  Target Release: 19.10
  Target Kernel: 5.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1835349/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1704310] Re: [Bug] Crystal Ridge - null pointer de-reference in device unregister path

[quanxian]

00289cd87676 6de5d06e657a 700cd033a82d 87a30e1f05d7 8aac0e233891
b70d31d054ee ca6bf264f6d8

v5.3-rc2

** Changed in: intel
   Status: Triaged => Fix Committed

** Description changed:

  Description:
  
  If I run the following script in a loop, and then ctrl-c it, the kernel
  hits a BUG in the device unregister path.
  
  --[ns-reconf.sh]--
  function pmem_btt_dax_switch() {
  sector_size_list="512 520 528 4096 4104 4160 4224"
  for sector_size in $sector_size_list; do
  ndctl create-namespace -f -e namespace$
  {1}.0 --mode=sector -l $sector_size
  ndctl create-namespace -f -e namespace${1}
  
  .0 --mode=raw
  ndctl create-namespace -f -e namespace$
  {1}
  
  .0 --mode=dax
  done
  }
  for i in 0 1 2 3; do
  pmem_btt_dax_switch $i &
  done
  --[ns-reconf.sh]--
  
  while true; do ./ns-reconfig.sh 0; ./ns-reconfig.sh 1; done
  
  I've tried three times and hit the bug every time, so it seems readily
  reproducible.
  
  Offset 0x20 is the put function pointer in struct klist. This is where
  the null pointer is triggered:
  
  static void klist_put(struct klist_node *n, bool kill)
  {
  struct klist *k = knode_klist;
  void (*put)(struct klist_node *) = k->put; <
  
  This is the tip of Linus' tree, commit be941bf2e6a32.
  
  Any ideas?
  
  -Jeff
  
  [ 117.728323] pmem0s: detected capacity change from 0 to 34093219840
  [ 117.831496] BUG: unable to handle kernel NULL pointer dereference at 
0020
  [ 117.867193] IP: klist_put+0x1b/0x70
  [ 117.884172] PGD 0
  [ 117.884172] P4D 0
  [ 117.894325]
  [ 117.912779] Oops:  1 SMP
  [ 117.926842] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 tun bridge 
stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter 
intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm 
vfat fat irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
aesni_intel crypto_simd nd_pmem iTCO_wdt iTCO_vendor_support glue_helper 
dax_pmem hpilo device_dax lpc_ich hpwdt cryptd nd_btt pcspkr ipmi_si sg ioatdma 
i2c_i801 mfd_core shpchp ipmi_devintf dca wmi ipmi_msghandler nfit 
acpi_power_meter nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables xfs 
sr_mod sd_mod cdrom mgag200 i2c_algo_bit drm_kms_helper syscopyarea
  [ 118.247253] sysfillrect sysimgblt bnx2x fb_sys_fops ahci tg3 mdio ttm 
libahci ptp drm libata i2c_core pps_core hpsa libcrc32c crc32c_intel 
scsi_transport_sas dm_mirror dm_region_hash dm_log dm_mod
  [ 118.326324] CPU: 45 PID: 1060 Comm: kworker/u145:2 Not tainted 4.12.0-rc2+ 
#28
  [ 118.358984] Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS 
P89 10/05/2016
  [ 118.398735] Workqueue: events_unbound async_run_entry_fn
  [ 118.426362] task: 880465ea8000 task.stack: c9000683c000
  [ 118.452949] RIP: 0010:klist_put+0x1b/0x70
  [ 118.470906] RSP: 0018:c9000683fd70 EFLAGS: 00010246
  [ 118.494545] RAX: 880cfdbe8b40 RBX:  RCX: 
00018022001c
  [ 118.526532] RDX: 00018022001d RSI: 0001 RDI: 

  [ 118.558720] RBP: c9000683fd90 R08: 88106463a8e8 R09: 
00018022001c
  [ 118.590772] R10: 6463a701 R11: 88106463a8e8 R12: 
88106935cc00
  [ 118.622923] R13: 880cfdbe8b68 R14: 0001 R15: 
88046f438ce8
  [ 118.655122] FS: () GS:88046fac() 
knlGS:
  [ 118.691517] CS: 0010 DS:  ES:  CR0: 80050033
  [ 118.716914] CR2: 0020 CR3: 01c09000 CR4: 
003406e0
  [ 118.749349] DR0:  DR1:  DR2: 

  [ 118.781627] DR3:  DR6: fffe0ff0 DR7: 
0400
  [ 118.814621] Call Trace:
  [ 118.825740] klist_del+0xe/0x10
  [ 118.839764] device_del+0x11a/0x330
  [ 118.855526] device_unregister+0x1a/0x60
  [ 118.873549] nd_async_device_unregister+0x22/0x30
  [ 118.895091] async_run_entry_fn+0x39/0x170
  [ 118.916718] process_one_work+0x149/0x360
  [ 118.937472] worker_thread+0x4d/0x3c0
  [ 118.953919] kthread+0x109/0x140
  [ 118.968400] ? rescuer_thread+0x380/0x380
  [ 118.986373] ? kthread_park+0x60/0x60
  [ 119.002425] ret_from_fork+0x2c/0x40
  [ 119.018421] Code: e9 1a ff ff ff 90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 
e5 41 56 41 89 f6 41 55 49 89 fd 41 54 53 48 8b 1f 48 83 e3 fe 48 89 df <4c> 8b 
63 20 e8 7c f8 00 00 45 84 f6 75 31 4c 89 ef e8 af fe ff
  [ 119.103298] RIP: klist_put+0x1b/0x70 RSP: c9000683fd70
  [ 119.128194] CR2: 0020
  [ 119.143813] --[ end trace 4fadffd9ed599da8 ]--
  [ 119.169828] Kernel panic - not syncing: Fatal exception
  [ 119.193524] Kernel Offset: disabled
  [ 119.213732] ---[ end Kernel panic - not syncing: Fatal exception
  
- Target Kernel:TBD
+ Target Kernel:5.3
  Target Release: 19.10

-- 
You received this bug notification because yo

[Kernel-packages] [Bug 1835138] Re: MKTME: make encrypted memory accessible by kernel

[quanxian]

** Description changed:

  Description:
  Direct mapping is not good for accessing encrypted pages as all memory is 
mapped with KeyID 0.
  
  We need the temporary mapping with correct KeyID. kmap()/kmap_atomic()
  API seems fill our needs.
  
  Target Release: 19.10
- Target Kernel: TBD
+ Target Kernel: 5.4

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1835138

Title:
  MKTME: make encrypted memory accessible by kernel

Status in intel:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:
  Direct mapping is not good for accessing encrypted pages as all memory is 
mapped with KeyID 0.

  We need the temporary mapping with correct KeyID. kmap()/kmap_atomic()
  API seems fill our needs.

  Target Release: 19.10
  Target Kernel: 5.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1835138/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1835347] Re: device_dax - export a 'resource' attribute for dax devices

[quanxian]

Merged in v5.3-rc1


commit 40cdc60ac16a42eb4e013f84d0e7aa1d6ee060d3
Author: Vishal Verma 
Date: Thu Jun 20 18:40:38 2019 -0600

device-dax: Add a 'resource' attribute

device-dax based devices were missing a 'resource' attribute to indicate
the physical address range contributed by the device in question. This
information is desirable to userspace tooling that may want to use the
dax device as system-ram, and wants to selectively hotplug and online
the memory blocks associated with a given device.

Without this, the tooling would have to parse /proc/iomem for the memory
ranges contributed by dax devices, which can be a workaround, but it is
far easier to provide this information in the sysfs hierarchy.

Cc: Dave Hansen 
Cc: Dan Williams 
Signed-off-by: Vishal Verma 
Signed-off-by: Dan Williams 

** Changed in: intel
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1835347

Title:
  device_dax - export a 'resource' attribute for dax devices

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:
  device_dax devices need to export a resource attribute so that libdaxctl
  can use it to find the address range for the device. This is required for
  onlining/offlining memory associated with a device in the system-ram mode
  (i.e. kmem).

  Target Release: 19.10
  Target Kernel: 5.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1835347/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1855399] Re: [TGL] graphics kernel support

[quanxian]

hi, Timo

have you integrated into 20.04? if so, we can think Ubuntu 20.04 support
TGL graphics. Not sure if you integrated into 20.04 or 20.04-oem?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1855399

Title:
  [TGL] graphics kernel support

Status in intel:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:

  This feature tracks the updates TGL graphics updates.

  We will submit the commit id lists since 5.4.

  20.04 will use v5.4 as a base, (2109/11/25)

  first commit lists will be provided in 2020/01, if you need more
  before that, please let us know.

  Target Release: 20.10
  Target Kernel: v5.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1855399/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1855399] Re: [TGL] graphics kernel support

[quanxian]

from our testing of beta release, seems TGL graphics is not supported in
Ubuntu 20.04 Beta release.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1855399

Title:
  [TGL] graphics kernel support

Status in intel:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:

  This feature tracks the updates TGL graphics updates.

  We will submit the commit id lists since 5.4.

  20.04 will use v5.4 as a base, (2109/11/25)

  first commit lists will be provided in 2020/01, if you need more
  before that, please let us know.

  Target Release: 20.10
  Target Kernel: v5.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1855399/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1872398] [NEW] [TGL] turbostat support

[quanxian]

Public bug reported:

Description:
Turbostat is a Linux tool to observe proper operation of Intel(R) Turbo Boost 
Technology.
Turbostat displays actual processor frequency and idle power state on modern 
x86 processors supporting invariant TSC, plus APERF and MPERF MSRs.


Upstream in Linux-5.6

author Chen Yu  2020-01-14 12:04:55 +0800
committer Len Brown  2020-03-20 00:32:27 -0400
commit 4bf7132a0ace398af8cec6485ee4c6db5ea8 (patch)
tree c2e7dc88595f9f01bb1d1d36bec46fdac7e30147 
/tools/power/x86/turbostat/turbostat.c
parent d8d005ba6afa502ca37ced5782f672c4d2fc1515 (diff)
download linux-4bf7132a0ace398af8cec6485ee4c6db5ea8.tar.gz
tools/power turbostat: Support Tiger Lake
>From a turbostat point of view, Tiger Lake looks like Ice Lake.

Signed-off-by: Chen Yu 
Signed-off-by: Len Brown 

** Affects: intel
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: intel-kernel-20.04

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1872398

Title:
  [TGL] turbostat support

Status in intel:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:
  Turbostat is a Linux tool to observe proper operation of Intel(R) Turbo Boost 
Technology.
  Turbostat displays actual processor frequency and idle power state on modern 
x86 processors supporting invariant TSC, plus APERF and MPERF MSRs.

  
  Upstream in Linux-5.6

  author Chen Yu  2020-01-14 12:04:55 +0800
  committer Len Brown  2020-03-20 00:32:27 -0400
  commit 4bf7132a0ace398af8cec6485ee4c6db5ea8 (patch)
  tree c2e7dc88595f9f01bb1d1d36bec46fdac7e30147 
/tools/power/x86/turbostat/turbostat.c
  parent d8d005ba6afa502ca37ced5782f672c4d2fc1515 (diff)
  download linux-4bf7132a0ace398af8cec6485ee4c6db5ea8.tar.gz
  tools/power turbostat: Support Tiger Lake
  From a turbostat point of view, Tiger Lake looks like Ice Lake.

  Signed-off-by: Chen Yu 
  Signed-off-by: Len Brown 

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1872398/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1842462] Re: [IOMMU] xsaves support for pasid

[quanxian]

** Description changed:

  Description
  context switch support for pasid using xsaves method.
  
  Target Release: 20.04
- Target Kernel: 5.6
+ Target Kernel: 5.7

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842462

Title:
  [IOMMU] xsaves support for pasid

Status in intel:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description
  context switch support for pasid using xsaves method.

  Target Release: 20.04
  Target Kernel: 5.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1842462/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1842681] Re: ACPI Errors with 8-socket DCPMM system

[quanxian]

** Changed in: intel
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842681

Title:
  ACPI Errors with 8-socket DCPMM system

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description
  A customer reporting ACPI errors during Linux boot in an 8 socket glueless 
system with 6 DCPMM modules installed per socket. After OS has completed 
initialization, any attempt to use NDCTL or IPMCTL results in a process or 
system hang.  The system boots and the apps are ok when reducing the system 
configuration to 6 sockets. Log extract is below.

  A web search turned up what looks like the same problem.  See
  https://lkml.org/lkml/2019/5/30/1290. This link describes a kernel
  change to increase the dimensions of the failing table. Your names
  appears in the signed-off of this link

  Can you confirm if it is the same problem described below (it looks like it 
is) and if the proposed kernel change describe in the link is the correction?
  Customer has checked kernel.org and the latest versions of the affected files 
do not have kernel change.

  They are validating RedHat and Suse Enterprise for 8+ socket system with 
maximum DCPMMs installed.
  Are there other items that must be updated to go along with the kernel change?

  These messages are extracted from the start-up log showing the OS and Kernel 
versions plus the ACPI errors.
  Welcome to SUSE Linux Enterprise Server 12 SP4  (x86_64) - Kernel 
4.12.14-94.41-default (ttyS0).

  ACPI Error: Could not allocate new OwnerId (255 max),
  AE_OWNER_ID_LIMIT (20170303/utownerid-149)

  Merged for v5.4:

  67a72420a326 ACPICA: Increase total number of possible Owner IDs

  Target Release: 20.04
  Target Kernel: 5.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1842681/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1850229] Re: [CML-U] new network device support- e1000e: Add support for Comet Lake:

[quanxian]

** Changed in: intel
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1850229

Title:
  [CML-U] new network device support- e1000e: Add support for Comet
  Lake:

Status in HWE Next:
  Fix Released
Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:
  e1000e: network support for CML

  
  This patch on intel-wired-lan enables CML support: [v1] e1000e: Add support 
for Comet Lake: https://patchwork.ozlabs.org/patch/1174394/. It is not on 
net-next yet. 

  Keep tune until it is in upstream.

  target kernel: 5.4
  target release: 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1850229/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1848977] Re: 5-level paging: enable 5-level paging in hardware

[quanxian]

2f13eb7c580fcbe3d73ebbe6fb1841381cad0a05 
59103caa6839592788e7ad58b35863aac034631a 
5e3b4a15dd8da6bded2092694c8db3b505cbf711 
f1ac10c24efbbcba0f8dae37ee90d45847f5c5af
v4.16

** Changed in: intel
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1848977

Title:
  5-level paging: enable 5-level paging in hardware

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:

  Need add kernel configuration to enable this feature. Enable
  CONFIG_X86_5LEVEL

  Test process of 19.10

  root@ubuntu:~/check_5level_page# cat /boot/config-5.4.0-rc2+ | grep 
CONFIG_X86_5LEVEL
  # CONFIG_X86_5LEVEL is not set
  root@ubuntu:~/check_5level_page# cat /proc/cpuinfo | grep la57
  root@ubuntu:~/check_5level_page#

  
  The IOMMU hardware is also changing with 5-level paging. This item is to 
track the work that needs to be done to update the IOMMU code for the new 
5-level tables.

  The IOMMU code is also substantially more abstracted than the plain
  pagetable code, and it may be able to handle the extra level and
  address space with few or no changes. It's possible this will simply
  become a validation activity.

  Target Release: 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1848977/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1844559] Re: [GLK-R]enable CPUID

[quanxian]

** Changed in: intel
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1844559

Title:
  [GLK-R]enable CPUID

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released

Bug description:
  Description
  CPUID for GLK-R is configured as 0x706A8 in platform BIOS

  Target Release: 20.04
  Target Kernel: TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1844559/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1862278] Re: [ACPI][FAN] Augment fan driver with _FPS information

[quanxian]

** Changed in: intel
   Status: New => Fix Committed

** Description changed:

  Description:
  
  To better support fan control in DPTF, we need the ACPI fan driver to
  expose additional information from BIOS/coreboot. Many designs now
  populate the _FPS object with read-only fan performance states. The
  entire contents of this object need to be exposed to user-space for
  thermal management software such as DPTF to better control the fan.
  
  Commit Ids:
  
  d19e470b6605c900db21fc7b34c66b6891a79983
  
  Target Kernel: 5.6
- Target Release: 20.04
+ Target Release: 20.10

** Tags removed: intel-kernel-20.04
** Tags added: intel-kernel-20.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1862278

Title:
  [ACPI][FAN] Augment fan driver with _FPS information

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:

  To better support fan control in DPTF, we need the ACPI fan driver to
  expose additional information from BIOS/coreboot. Many designs now
  populate the _FPS object with read-only fan performance states. The
  entire contents of this object need to be exposed to user-space for
  thermal management software such as DPTF to better control the fan.

  Commit Ids:

  d19e470b6605c900db21fc7b34c66b6891a79983

  Target Kernel: 5.6
  Target Release: 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1862278/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1859538] Re: Harrison Peak wifi / BT support

[quanxian]

** Changed in: intel
   Status: Won't Fix => Fix Released

** Description changed:

  Description:
  
  HrP2 will be supported in CML/TGL platform.
  
- 
  Target Release: 20.04
- Target Kernel: 5.6
+ Target Kernel: 5.4

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1859538

Title:
  Harrison Peak  wifi / BT support

Status in HWE Next:
  New
Status in intel:
  Fix Released
Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:

  HrP2 will be supported in CML/TGL platform.

  Target Release: 20.04
  Target Kernel: 5.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1859538/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1848978] Re: CML: perf enabling for core

[quanxian]

** Changed in: intel
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1848978

Title:
  CML: perf enabling for core

Status in intel:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-osp1 source package in Focal:
  Confirmed

Bug description:
  [SRU Justification]

  [Impact]
  There is no complete perf support for Comet Lake CPU. For Ice Lake, some
  changes has been included in v5.3, but still misses CPU IDs.

  [Fix]
  perf support for Comet Lake is based on previous works for Ice Lake, so
  changes for both have to be backported.

  [Test Case]
  On platforms with Comet Lake/Ice Lake CPUs, one should find new
  cstate_pkg events c{8,9,10}-residency appear in output of `perf list`
  for use.

  [Regression Potential]
  Low. This backports perf support for previously incompletedly supported
  cpu models.

  == original bug description ==

  Description:

  CML perf enabling for core

  v5.4-rc3
  1ffa6c04dae39776a3c222bdf88051e394386c01 
9066288b2aab1804dc1eebec6ff88474363b89cb 
9674b1cc0f94c34f76e58c102623a866836f269e

  Target Kernel: 5.4
  Target Release: 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1848978/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1859538] Re: Harrison Peak wifi / BT support

[quanxian]

BT is verified in Ubuntu 20.04 LTS, works well. TGL (Harrison Peak)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1859538

Title:
  Harrison Peak  wifi / BT support

Status in HWE Next:
  New
Status in intel:
  Fix Released
Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:

  HrP2 will be supported in CML/TGL platform.

  Target Release: 20.04
  Target Kernel: 5.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1859538/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1834558] Re: intel_idle enable in ICL

[quanxian]

** Description changed:

  Description:
  
  Support for intel_idle on Ice Lake (client)
  
- Target Release: 20.04
- Target Kernel: 5.4
+ Target Release: 20.10
+ Target Kernel: 5.6

** Tags removed: intel-kernel-19.10
** Tags added: intel-kernel-20.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1834558

Title:
  intel_idle enable in ICL

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  New

Bug description:
  Description:

  Support for intel_idle on Ice Lake (client)

  Target Release: 20.10
  Target Kernel: 5.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1834558/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp