DPDK patches and discussions
 help / color / mirror / Atom feed
From: Arnon Warshavsky <arnon@qwilt.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	"Burakov, Anatoly" <anatoly.burakov@intel.com>,
	wenzhuo.lu@intel.com,  declan.doherty@intel.com,
	jerin.jacob@caviumnetworks.com,  ferruh.yigit@intel.com,
	dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] eal: replace rte_panic instances to return an error value
Date: Tue, 27 Mar 2018 17:06:24 +0300	[thread overview]
Message-ID: <CAKy9EB2-fMoZuoX=78PEy5fY2CJ0hFto7_QiqnSsAwk17CwJKw@mail.gmail.com> (raw)
In-Reply-To: <CAKy9EB0jS7-guPRnQvrhZqaF3hsE9B121CDpYGiOyibe762X1w@mail.gmail.com>

I now have a set of several patches which pass the abi-validation , 1 patch
of checkpatches.sh to prevent future panic instances
and the set of abi-breaking changes which are included the init sequence.

1.
I assume it is best to bundle all to a single patchset. Please correct me
otherwise

2.
Trying to work around the abi in this phase
What is your take regarding adding a state to the init phase:

int rte_get_legacy_panic_state();
void rte_move_to_legacy_panic_state();

This will allow preserving abi for these few functions, replacing for
example the currently abi-breaking

if (eal_thread_init_master())
    return -1

with

eal_thread_init_master()
if ( rte_get_legacy_panic_state())
    return -1

while calling  rte_move_to_legacy_panic_state()  from within these void
functions where panic takes place today.

This can also partially serve the cases where panic is called from within
an interrupt handler, and have no applicative context to return to.

thanks
/Arnon

      reply	other threads:[~2018-03-27 14:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20 21:53 Arnon Warshavsky
2018-03-21  9:11 ` Bruce Richardson
2018-03-21  9:17   ` Arnon Warshavsky
2018-03-27 14:06     ` Arnon Warshavsky [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='CAKy9EB2-fMoZuoX=78PEy5fY2CJ0hFto7_QiqnSsAwk17CwJKw@mail.gmail.com' \
    --to=arnon@qwilt.com \
    --cc=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=thomas@monjalon.net \
    --cc=wenzhuo.lu@intel.com \
    /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).