From: Jason Wang <jasowang@redhat.com>
To: andrew@daynix.com, qemu-devel@nongnu.org
Cc: dmitry.fleytman@gmail.com
Subject: Re: [PATCH 1/1] e1000e: Added ICR clearing by corresponding IMS bit.
Date: Fri, 29 May 2020 15:35:03 +0800 [thread overview]
Message-ID: <7d8202a5-58ad-d7e9-db29-3316834547b8@redhat.com> (raw)
In-Reply-To: <57ab1532-c3a6-e631-5b0e-e89fc4d82873@redhat.com>
On 2020/5/29 下午3:18, Jason Wang wrote:
>
> On 2020/5/13 下午7:31, andrew@daynix.com wrote:
>> From: Andrew Melnychenko <andrew@daynix.com>
>>
>> Buglink: https://bugzilla.redhat.com/show_bug.cgi?id=1707441
>> Added ICR clearing if there is IMS bit - according to the note by
>> section 13.3.27 of the 8257X developers manual.
>>
>> Signed-off-by: Andrew Melnychenko <andrew@daynix.com>
>> ---
>> hw/net/e1000e_core.c | 10 ++++++++++
>> hw/net/trace-events | 1 +
>> 2 files changed, 11 insertions(+)
>>
>> diff --git a/hw/net/e1000e_core.c b/hw/net/e1000e_core.c
>> index d5676871fa..10212d7932 100644
>> --- a/hw/net/e1000e_core.c
>> +++ b/hw/net/e1000e_core.c
>> @@ -2624,6 +2624,16 @@ e1000e_mac_icr_read(E1000ECore *core, int index)
>> e1000e_clear_ims_bits(core, core->mac[IAM]);
>> }
>> + /*
>> + * PCIe* GbE Controllers Open Source Software Developer's Manual
>> + * 13.3.27 Interrupt Cause Read Register
>> + */
>> + if ((core->mac[ICR] & E1000_ICR_ASSERTED) &&
>> + (core->mac[ICR] & core->mac[IMS])) {
>> + trace_e1000e_irq_icr_clear_icr_bit_ims(core->mac[ICR],
>> core->mac[IMS]);
>> + core->mac[ICR] = 0;
>> + }
>> +
>
>
> Hi Andrew:
>
> So my comments still. I think we need to implement 82574l behavior (if
> you go through e1000e.c all chapters it mentioned is for 82574l
> datasheet not the one you pointed to me).
>
> And actually the 82574l behavior is much more simpler.
To be more specific.
See chapter 7.4.5 which describes the ICR clearing.
It has three methods for clearing: auto-clear, clear-on-write and
clear-on-read.
And in the part of "Read to clear" it said:
"""
All bits in the ICR register are cleared on a read to ICR.
"""
So there's no need to IMS and other stuffs here.
Thanks
>
> Thanks
next prev parent reply other threads:[~2020-05-29 7:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 11:31 [PATCH 0/1] e1000e: Added ICR clearing by corresponding IMS bit andrew
2020-05-13 11:31 ` [PATCH 1/1] " andrew
2020-05-29 7:18 ` Jason Wang
2020-05-29 7:35 ` Jason Wang [this message]
2020-06-01 16:47 ` Andrew Melnichenko
2020-06-02 2:14 ` Jason Wang
-- strict thread matches above, loose matches on Subject: below --
2020-05-13 11:28 [PATCH 0/1] " andrew
2020-05-13 11:28 ` [PATCH 1/1] " andrew
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=7d8202a5-58ad-d7e9-db29-3316834547b8@redhat.com \
--to=jasowang@redhat.com \
--cc=andrew@daynix.com \
--cc=dmitry.fleytman@gmail.com \
--cc=qemu-devel@nongnu.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).