linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Lombard <clombard@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, fbarrat@linux.vnet.ibm.com,
	imunsie@au1.ibm.com, andrew.donnellan@au1.ibm.com
Subject: [PATCH 2/7] cxl: Remove unused values in bare-metal environment.
Date: Wed,  1 Feb 2017 18:30:08 +0100	[thread overview]
Message-ID: <1485970213-25532-3-git-send-email-clombard@linux.vnet.ibm.com> (raw)
In-Reply-To: <1485970213-25532-1-git-send-email-clombard@linux.vnet.ibm.com>

The two fields pid and tid of the structure cxl_irq_info are only used
in the guest environment. To avoid confusion, it's not necessary
to fill the fields in the bare-metal environment.
The PSL Process and Thread Identification Register is only used when
attaching a dedicated process for PSL8 only.

Signed-off-by: Christophe Lombard <clombard@linux.vnet.ibm.com>
---
 drivers/misc/cxl/native.c | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/drivers/misc/cxl/native.c b/drivers/misc/cxl/native.c
index 09505f4..8a3ce99 100644
--- a/drivers/misc/cxl/native.c
+++ b/drivers/misc/cxl/native.c
@@ -858,8 +858,6 @@ static int native_detach_process(struct cxl_context *ctx)
 
 static int native_get_irq_info(struct cxl_afu *afu, struct cxl_irq_info *info)
 {
-	u64 pidtid;
-
 	/* If the adapter has gone away, we can't get any meaningful
 	 * information.
 	 */
@@ -869,9 +867,6 @@ static int native_get_irq_info(struct cxl_afu *afu, struct cxl_irq_info *info)
 	info->dsisr = cxl_p2n_read(afu, CXL_PSL_DSISR_An);
 	info->dar = cxl_p2n_read(afu, CXL_PSL_DAR_An);
 	info->dsr = cxl_p2n_read(afu, CXL_PSL_DSR_An);
-	pidtid = cxl_p2n_read(afu, CXL_PSL_PID_TID_An);
-	info->pid = pidtid >> 32;
-	info->tid = pidtid & 0xffffffff;
 	info->afu_err = cxl_p2n_read(afu, CXL_AFU_ERR_An);
 	info->errstat = cxl_p2n_read(afu, CXL_PSL_ErrStat_An);
 	info->proc_handle = 0;
-- 
2.7.4

  parent reply	other threads:[~2017-02-01 17:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01 17:30 [PATCH 0/7] cxl: Add support for Coherent Accelerator Interface Architecture 2.0 Christophe Lombard
2017-02-01 17:30 ` [PATCH 1/7] cxl: Read vsec perst load image Christophe Lombard
2017-02-02  4:15   ` Andrew Donnellan
2017-02-01 17:30 ` Christophe Lombard [this message]
2017-02-02  4:16   ` [PATCH 2/7] cxl: Remove unused values in bare-metal environment Andrew Donnellan
2017-02-01 17:30 ` [PATCH 3/7] cxl: Keep track of mm struct associated with a context Christophe Lombard
2017-02-28  7:44   ` Andrew Donnellan
     [not found]     ` <66dee4f8-5897-2948-5813-c021b83379f8@linux.vnet.ibm.com>
2017-03-20  2:09       ` Andrew Donnellan
2017-02-01 17:30 ` [PATCH 4/7] cxl: Update implementation service layer Christophe Lombard
2017-03-02  6:48   ` Andrew Donnellan
2017-02-01 17:30 ` [PATCH 5/7] cxl: Rename some psl8 specific functions Christophe Lombard
2017-03-02  6:55   ` Andrew Donnellan
2017-02-01 17:30 ` [PATCH 6/7] cxl: Isolate few psl8 specific calls Christophe Lombard
2017-03-03  7:06   ` Andrew Donnellan
2017-02-01 17:30 ` [PATCH 7/7] cxl: Add psl9 specific code Christophe Lombard
2017-03-02  6:55   ` Andrew Donnellan
2017-03-03  7:10   ` Andrew Donnellan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1485970213-25532-3-git-send-email-clombard@linux.vnet.ibm.com \
    --to=clombard@linux.vnet.ibm.com \
    --cc=andrew.donnellan@au1.ibm.com \
    --cc=fbarrat@linux.vnet.ibm.com \
    --cc=imunsie@au1.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).