From: Juan Quintela <quintela@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Akihiko Odaki <akihiko.odaki@daynix.com>,
qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>,
Dmitry Fleytman <dmitry.fleytman@gmail.com>
Subject: Re: [PATCH for 8.0] igb: Save the entire Tx context descriptor
Date: Thu, 16 Mar 2023 15:45:18 +0100 [thread overview]
Message-ID: <87bkkslpq9.fsf@secure.mitica> (raw)
In-Reply-To: <e43d9dde-1eed-b8ae-6d37-b1ee1b65a569@linaro.org> ("Philippe Mathieu-Daudé"'s message of "Thu, 16 Mar 2023 13:46:08 +0100")
Philippe Mathieu-Daudé <philmd@linaro.org> wrote:
> On 16/3/23 13:40, Akihiko Odaki wrote:
>> On 2023/03/16 21:36, Philippe Mathieu-Daudé wrote:
>>> On 16/3/23 13:28, Akihiko Odaki wrote:
>>>> The current implementation of igb uses only part of a advanced Tx
>>>> context descriptor because it misses some features and sniffs the trait
>>>> of the packet instead of respecting the packet type specified in the
>>>> descriptor. However, we will certainly need the entire Tx context
>>>> descriptor when we update igb to respect these ignored fields. Save the
>>>> entire Tx context descriptor to prepare for such a change.
>>>>
>>>> Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
>>>> ---
>>>> hw/net/igb.c | 6 ++++--
>>>> hw/net/igb_core.c | 17 ++++++++++-------
>>>> hw/net/igb_core.h | 3 +--
>>>> 3 files changed, 15 insertions(+), 11 deletions(-)
>>>>
>>>> diff --git a/hw/net/igb.c b/hw/net/igb.c
>>>> index 0792626322..50239a7cb1 100644
>>>> --- a/hw/net/igb.c
>>>> +++ b/hw/net/igb.c
>>>> @@ -499,8 +499,10 @@ static const VMStateDescription igb_vmstate_tx = {
>>>> .version_id = 1,
>>>
>>> Don't we need to increment the vmstate version? See
>>> https://qemu-project.gitlab.io/qemu/devel/migration.html#versions
>> This device is added only a week ago so it shouldn't need version
>> bump. That is also why I tagged this change "for 8.0".
>
> Well it is cheaper than dealing with partially backported commits...
> Also could be a better example for future developers IMHO. My 2 cents.
You can't have everything O:-)
I would just bump the version and not do the "dance" where you can
migrate from v1 and v2. I.e. don't add tests at all.
This way bisect will fail with the correct message.
Later, Juan.
prev parent reply other threads:[~2023-03-16 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 12:28 [PATCH for 8.0] igb: Save the entire Tx context descriptor Akihiko Odaki
2023-03-16 12:36 ` Philippe Mathieu-Daudé
2023-03-16 12:40 ` Akihiko Odaki
2023-03-16 12:46 ` Philippe Mathieu-Daudé
2023-03-16 14:45 ` Juan Quintela [this message]
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=87bkkslpq9.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=akihiko.odaki@daynix.com \
--cc=dmitry.fleytman@gmail.com \
--cc=jasowang@redhat.com \
--cc=philmd@linaro.org \
--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).