diff options
| author | Eric Farman <farman@linux.ibm.com> | 2025-11-07 03:49:27 +0100 |
|---|---|---|
| committer | Janosch Frank <frankja@linux.ibm.com> | 2025-11-21 10:33:57 +0100 |
| commit | 44acac00be5dbda58f337acda41148d39743075c (patch) | |
| tree | 72f438b7a2f0774ce5af66cd0f6df367871af4ad /tools/perf/scripts/python/net_dropmonitor.py | |
| parent | 8e8678e740ecde2ae4a0404fd9b4ed2b726e236d (diff) | |
| download | kernel-44acac00be5dbda58f337acda41148d39743075c.tar.gz | |
KVM: s390: vsie: Check alignment of BSCA header
The VSIE code currently checks that the BSCA struct fits within
a page, and returns a validity exception 0x003b if it doesn't.
The BSCA is pinned in memory rather than shadowed (see block
comment at end of kvm_s390_cpu_feat_init()), so enforcing the
CPU entries to be on the same pinned page makes sense.
Except those entries aren't going to be used below the guest,
and according to the definition of that validity exception only
the header of the BSCA (everything but the CPU entries) needs to
be within a page. Adjust the alignment check to account for that.
Signed-off-by: Eric Farman <farman@linux.ibm.com>
Reviewed-by: Christian Borntraeger <borntraeger@linux.ibm.com>
Reviewed-by: Christoph Schlameuss <schlameuss@linux.ibm.com>
Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions