[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190430113718.426392f0.pasic@linux.ibm.com>
Date: Tue, 30 Apr 2019 11:37:18 +0200
From: Halil Pasic <pasic@...ux.ibm.com>
To: Pierre Morel <pmorel@...ux.ibm.com>
Cc: borntraeger@...ibm.com, alex.williamson@...hat.com,
cohuck@...hat.com, linux-kernel@...r.kernel.org,
linux-s390@...r.kernel.org, kvm@...r.kernel.org,
frankja@...ux.ibm.com, akrowiak@...ux.ibm.com, david@...hat.com,
schwidefsky@...ibm.com, heiko.carstens@...ibm.com,
freude@...ux.ibm.com, mimu@...ux.ibm.com
Subject: Re: [PATCH v7 3/4] s390: ap: implement PAPQ AQIC interception in
kernel
On Tue, 30 Apr 2019 10:32:52 +0200
Pierre Morel <pmorel@...ux.ibm.com> wrote:
> >>> + aqic_gisa.gisa = gisa->next_alert >> 4;
> >>
> >> Why gisa->next_alert? Isn't this supposed to get set to gisa origin
> >> (without some bits on the left)?
s/left/right/
> >
> > Someone already asked this question.
It must have been in some previous iteration... Can you give me a
pointer?
> > The answer is: look at the ap_qirq_ctrl structure, you will see that the
> > gisa field is 27 bits wide.
My question was not about the width, but about gisa->next_alert being
used.
Regards,
Halil
Powered by blists - more mailing lists